Skip to contentSkip to conversation

PlugSched-6.5.1 for 2.6.22

RFC [email protected] 2 participants 2 messages Aug 16, 2007

lore
Share & tools
lore
#0 lore raw
Quoted 8 lines

Having a framework for giving people the choice between different solutions usually sounds good in theory, but in practice there's the often underestimated high price of people using a different solution instead of reporting a problem with one solution or people adding features to only one of the solutions resulting in different solutions having different features and bugs instead of one solution with all features and bug fixes.

Quoted 4 lines

So you should give a good technical explanation why it's not technically possible or not desirable for one solution to work well for everyone.

From a user`s point of view, i like PlugSched.

It gives the average or inexperienced user the ability to switch between different schedulers and it empowers him to compare between them easily.

I like choice.

Ok, its not good to have too much of that, but its always good to have at least one or two alternatives.

No patch and no compile orgy for the end-user anymore - he can try if a different scheduler makes his stuttering audio go away or if his desktop-environment is more responsive with "itchysched" than with "scratchysched".

Take this as a user`s vote for PlugSched.

There are pluggable I/O schedulers in Linux for years now, there was that switch from AS to CFQ as the default - so please give us pluggable CPU schedulers, too ! :)

roland

ps:
i trust you kernel developers know what you are doing, but if scares me a little bit, that some integral and living part like O(1) being ripped off and being replaced by something new.

Quoted 14 lines · Tong N
Quoted 7 lines · Al Boldi
Quoted 6 lines
Quoted 2 lines · Peter Williams

Probably the last one now that CFS is in the main line :-(.

What do you mean? A pluggable scheduler framework is indispensible

even

Quoted 4 lines

in

Quoted 1 line

the presence of CFS or SD.

Indeed, and I hope it gets merged, giving people the chance to test

out

Quoted 1 line

different schedulers easily, without having to do patching,

Quoted 8 lines

de-patching,

Quoted 2 lines

re-patching and blah blah blah.

Yes, such a framework would be invaluable, especially given that scheduling often has conflicting goals and different workloads have different requirements. No single solution fits all.
...

Having a framework for giving people the choice between different solutions usually sounds good in theory, but in practice there's the often underestimated high price of people using a different solution instead of reporting a problem with one solution or people adding features to only one of the solutions resulting in different solutions having different features and bugs instead of one solution with all features and bug fixes.

So you should give a good technical explanation why it's not technically possible or not desirable for one solution to work well for everyone.

cu
Adrian

Signature · 7 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
#1 lore raw
Quoted 3 lines · On Thu, 16 Aug 2007 22:42:42 +0200, [email protected] said:

i trust you kernel developers know what you are doing, but if scares me a little bit, that some integral and living part like O(1) being ripped off and being replaced by something new.

There's something even scarier - O(1) being taken out and replaced by multiple new things, none of which ever gets fully tested because if one misbehaves, the user says "so what" and tries another one without bothering to file a bug report...

Been there, done that - I found a timing hole in the pluggable I/O schedulers that probably nobody had managed to hit because there were 3 or 4 choices available, and they just set a default they liked. Turned out there was a race condition if I/O happened while schedulers were being swapped.