Various scheduler-related topics
Posted Sep 17, 2009 11:45 UTC (Thu) by hppnq
Parent article: Various scheduler-related topics
There is a good reason to run the parent first, though: the parent's state is active in the processor, the translation lookaside buffer (TLB) contains the right information, etc. So parent-runs-first should perform better. It appears that recent tests showed that parent-runs-first does, indeed, outperform child-runs-first on that most important benchmark: kernel builds. That was enough to get the default changed.
Ah, nostalgia... Here -- scroll down a bit -- the idea to run the child first was introduced, thinking that this would improve performance in many common cases, because it prevented unnecessary COWs when the child would not do very complicated things. Of course, Linus seemed to use lmbench instead of kernel builds. ;-)
Also, ESR released CML2-1.2.0!
to post comments)