PlugSched-6.5.1 for 2.6.22
Probably the last one now that CFS is in the main line :-(.
A patch for 2.6.22 is available at:
<http://downloads.sourceforge.net/cpuse/plugsched-6.5.1-for-2.6.22.patch>
Very Brief Documentation:
You can select a default scheduler at kernel build time. If you wish to boot with a scheduler other than the default it can be selected at boot time by adding:
cpusched=<scheduler>
to the boot command line where <scheduler> is one of: ingosched, ingo_ll, nicksched, staircase, spa_no_frills, spa_ws, spa_svr, spa_ebs or zaphod. If you don't change the default when you build the kernel the default scheduler will be ingosched (which is the normal scheduler).
The scheduler in force on a running system can be determined by the contents of:
/proc/scheduler
Control parameters for the scheduler can be read/set via files in:
/sys/cpusched/<scheduler>/
Peter
Signature · 4 lines
Peter Williams [email protected] "Learning, n. The kind of ignorance distinguishing the studious." -- Ambrose Bierce
Quoted 1 line · Peter Williams
Probably the last one now that CFS is in the main line :-(.
hm, why is CFS in mainline a problem? The CFS merge should make the life of development/test patches like plugsched conceptually easier. (it will certainly cause a lot of churn, but that's for the better i think.)
Most of the schedulers in plugsched should be readily adaptable to the modular scheduling-policy scheme of the upstream scheduler. I'm sure there will be some minor issues as isolation of the modules is not enforced right now - and i'd be happy to review (and potentially apply) common-sense patches that improve the framework.
Ingo
Quoted 5 lines · Ingo Molnar
Quoted 1 line · Peter Williams
Probably the last one now that CFS is in the main line :-(.
hm, why is CFS in mainline a problem?
It means a major rewrite of the plugsched interface and I'm not sure that it's worth it (if CFS works well). However, note that I did say probably not definitely :-). I'll play with it and see what happens.
Quoted 3 lines
The CFS merge should make the life
of development/test patches like plugsched conceptually easier. (it will certainly cause a lot of churn, but that's for the better i think.)
I don't think that is necessarily the case.
Quoted 3 lines
Most of the schedulers in plugsched should be readily adaptable to the modular scheduling-policy scheme of the upstream scheduler.
I don't think that this necessarily true. Ingosched and ingo_ll are definitely out and I don't feel like converting staircase and nicksched as I have no real interest in them. Perhaps I'll just create the interface and some schedulers based on my own ideas and let others such as Con and Nick add schedulers if they're still that way inclined.
Quoted 4 lines
I'm sure
there will be some minor issues as isolation of the modules is not enforced right now - and i'd be happy to review (and potentially apply) common-sense patches that improve the framework.
Thanks for the offer of support (it may sway my decision), Peter
Signature · 4 lines
Peter Williams [email protected] "Learning, n. The kind of ignorance distinguishing the studious." -- Ambrose Bierce
Quoted 10 lines · Peter Williams
Quoted 5 lines · Ingo Molnar
Quoted 1 line · Peter Williams
Probably the last one now that CFS is in the main line :-(.
hm, why is CFS in mainline a problem?
It means a major rewrite of the plugsched interface and I'm not sure that it's worth it (if CFS works well). However, note that I did say probably not definitely :-). I'll play with it and see what happens.
i think it's very useful as a constant reality check. Yes, i did periodically boot your Zaphod scheduler too on a testbox ;-) "CFS works well" cannot be determined reliably if there's nothing to compare it against. One goal behind the CFS changes was to remove the need for massive scheduler rewrites and to ease prototyping. Somehow there are lots of people who really love to hack the scheduler, those weirdos ;-)
Quoted 5 lines
Quoted 3 lines
The CFS merge should make the life of development/test patches like plugsched conceptually easier. (it will certainly cause a lot of churn, but that's for the better i think.)
I don't think that is necessarily the case.
well, kernel/sched_rt.c and kernel/sched_fair.c are already more different on a conceptual angle than any of the two schedulers in PlugSched i think. But ... i dont expect the initial port of PlugSched to be easy at all.
Quoted 9 lines
Quoted 2 lines
Most of the schedulers in plugsched should be readily adaptable to the modular scheduling-policy scheme of the upstream scheduler.
I don't think that this necessarily true. Ingosched and
ingo_llare definitely out and I don't feel like converting staircase and nicksched as I have no real interest in them. Perhaps I'll just create the interface and some schedulers based on my own ideas and let others such as Con and Nick add schedulers if they're still that way inclined.
Yeah, i think starting with a smaller subset is the right approach - i think people _will_ fill the gaps ;-) I agree that preserving "Ingosched" would not make much sense. (Although it could still be useful to someone who finds some regression and suspects CFS, and wants to try with the old scheduler. Or just to test/prove that the modularization is strong enough to even include those scheduler heuristics the old scheduler did. Or out of historic interest.)
Quoted 5 lines
Quoted 3 lines
I'm sure there will be some minor issues as isolation of the modules is not enforced right now - and i'd be happy to review (and potentially apply) common-sense patches that improve the framework.
Thanks for the offer of support (it may sway my decision),
you are welcome :) Dmitry Adamushko and Srivatsa Vaddagiri already did lots of nice "policy module isolation" work in CFS (since the first crude cut i did in CFS v1), both for the cleanup factor and to enable features like group-scheduling.
Ingo