Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Again... isn't it the same as the old-well-known "multilevel feedback queues" that appears in every OS book since MULTICS?
The staircase scheduler
Posted Jun 3, 2004 5:08 UTC (Thu) by error27 (subscriber, #8346)
If you want to learn more about the difficult issues for schedulers read
Con's write up here.
It's pretty weird to not have an expired array. It seems like a reasonable scheduler design because it obviously gives priority to interactive processes and it doesn't starve any processes. I can see how this would be simpler to code. It's a nice design. I guess the real proof is in testing. :)
Posted Jun 3, 2004 15:30 UTC (Thu) by gallir (guest, #5735)
Posted Jun 4, 2004 2:40 UTC (Fri) by error27 (subscriber, #8346)
Right. With both the regular scheduler and the stair case scheduler you have 140 queues that represent 140 different priorities. You execute the top priorities first in a round robin format. The trick with the stair case scheduler is the logic behind how the processes move from one queue to the other.
> There are a number of variations on this scheme.
Exactly. In some ways, you could say that this was "just" a new variation. But in other ways, it's a pretty inovative variation. ;)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds