* Mike Galbraith <[EMAIL PROTECTED]> wrote:
> [...] The situation as we speak is that you can run cpu intensive
> tasks while watching eye-candy. With RSDL, you can't, you feel the
> non-interactive load instantly. [...]
i have to agree with Mike that this is a material regression that cannot
be talked around.
Con, we want RSDL to /improve/ interactivity. Having new scheduler
interactivity logic that behaves /worse/ in the presence of CPU hogs,
which CPU hogs are even reniced to +5, than the current interactivity
code, is i think a non-starter. Could you try to fix this, please? Good
interactivity in the presence of CPU hogs (be them default nice level or
nice +5) is _the_ most important scheduler interactivity metric.
Anything else is really secondary.
Ingo
ps. please be nice to each other - both of you are long-time
scheduler contributors who did lots of cool stuff :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
