Jump to content

Adaptive partition scheduler

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 203.199.248.18 (talk) at 10:51, 19 July 2007. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Adapti[[Link titleBold text#REDIRECT [[


Insert text--203.199.248.18 10:51, 19 July 2007 (UTC)<math>Insert non-formatted text here</math>[[Media:[[Image:Example.ogg]] == [Headline text][[[http://www.hariharan.s.com link title]]] == ]]]]]]ve Partition Schedulers are a relatively
new











Strike-through textStrike-through text#REDIRECT [[--203.199.248.18 10:51, 19 July 2007 (UTC)Insert text <gallery> Insert non-formatted text here </gallery> <gallery> Image:Example.jpg|Caption1 Image:Example.jpg|Caption2{| class="wikitable" |- <math>! header 1 ! header 2 ! header 3 |- | row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |- | row 2, cell 1 | row 2, cell 2 | row 2, cell 3</math>[[Image: == Example.jpg == ]] |} </gallery>]]type of partition scheduler,

'''unga aayaa'''...................

pioneered with the most recent version of the QNX operating system. Adaptive Partitioning, or AP, allows the real-time system designer to request that a percentage of processing resources be reserved for a particular subsystem (group of threads and/or processes).  The operating systems priority driven pre-emptive scheduler will behave in the same way that a non-AP system would until the system is overloaded (i.e. system-wide there is more computation to perform, than the processor is capable of sustaining over the long term).  During overload, the AP scheduler enforces hard limits on total run-time for the subsystems within a partition, as dictated by the allocated percentage of processor bandwidth for the particular partition.

If the system is not overloaded, a partition that is allocated (for example) 10% of the processor bandwidth, can, in fact, use more than 10%, as it will borrow from the spare budget of other partitions (but will be required to pay it back later). This is very useful for the non real-time subsystems that experience variable load, since these subsystems can make use of spare budget from hard real-time partitions in order to make more forward progress than they would in a Fixed Partition Scheduler such as ARINC-653, but without impacting the hard real-time subsystems deadlines.

QNX 6.3 will have this feature.