Nick Piggin <piggin@xxxxxxxxxxxxxxx> wrote:
So it is quite sad that the scheduler in 2.6 is
sitting there doing nothing but waiting to be obsoleted, while Con's
good (and begnin) scheduler patches are waiting around and getting
less than 1% of the testing they need.
My concern is the (large) performance regression with specjbb and
volanomark, due to increased idle time.
We cannot just jam all this code into Linus's tree while crossing our
fingers and hoping that something will turn up to fix this problem. Because we don't know what causes it, nor whether we even _can_ fix it.
So this is the problem which everyone who is working on the CPU scheduler
should be concentrating on, please.