Comment Re:great news (Score 1) 333
Making schedulers runtime pluggable would make it really easy to get other people hacking on the Linux scheduler though.
For example, you could lash up a reusable test harness to allow scheduler testing under well defined and repeatable scenarios. This may then allow more direct comparison between schedulers hopefully leading to a best of breed race. Making it runtime un/loadable would also speed up the development cycle for the scheduler much in the same way that loadable modules can often be more rapidly debugged and fixed by not needing a reboot for each change.
You could even go crazy and make a scheduler plug in 'shim' just for the purpose of profiling different implementations under real workloads.
The only thing I would say is that the whole scheduler API should be made in such a way that the scheduler is undeniably covered by the GPL. Binary blob schedulers would be the worst possible outcome and would go against the thought of trying to open up the scheduler as a means of furthering development and healthy competition.