Re: sched_yield: delete sysctl_sched_compat_yield

[Mark Lord <lkml@rtr.ca>]

Ingo Molnar wrote:
> * Mark Lord <lkml@rtr.ca> wrote:
> 
>> Ack.  And what of the suggestion to try to ensure that a yielding task 
>> simply not end up as the very next one chosen to run?  Maybe by 
>> swapping it with another (adjacent?) task in the tree if it comes out 
>> on top again?
> 
> we did that too for quite some time in CFS - it was found to be "not 
> agressive enough" by some folks and "too agressive" by others. Then when 
> people started bickering over this we added these two simple corner 
> cases - switchable via a flag. (minimum agression and maximum agression)
> 
>> (I really don't know the proper terminology to use here, but hopefully 
>> Ingo can translate that).
> 
> the terminology you used is perfectly fine.
> 
>> Thanks Ingo -- I *really* like this scheduler!
> 
> heh, thanks :) For which workload does it make the biggest difference 
> for you? (and compared to what other scheduler you used before? 2.6.22?)
..

Heh.. I'm just a very unsophisticated desktop user, and I like it when
Thunderbird and Firefox are unaffected by the "make -j3" kernel builds
that are often running in another window.  BIG difference there.

And on the cool side, the Swarm game (swarm.swf) is a great example of
something that used to get jerky really fast whenever anything else was
running, and now it really doesn't seem to be affected by anything.
(I don't really play computer games, but this one is has a very retro feel..).

Cheers