Re: [SCHED] wrong priority calc - SIMPLE test case
From: Con Kolivas
Date: Sat Dec 31 2005 - 06:11:08 EST
On Saturday 31 December 2005 21:52, Paolo Ornati wrote:
> On Sat, 31 Dec 2005 11:34:46 +0100
>
> Paolo Ornati <ornati@xxxxxxxxxxxxx> wrote:
> > > It is a patch against the 2.6.15-rc7 kernel and includes some other
> > > scheduling patches from the -mm kernels.
> >
> > Yes, this fixes both my test-case (transcode & little program), they
> > get priority 25 instead of ~16.
> >
> > But the priority of DD is now ~23 and so it still suffers a bit:
>
> I forgot to mention that even the others "interactive" processes
> don't get a good priority too.
>
> Xorg for example, while only moving the cursor around, gets priority
> 23/24. And when cpu-eaters are running (at priority 25) it isn't happy
> at all, the cursor begins to move in jerks and so on...
This is why Ingo, Nick and myself think that a tweak to the heavily field
tested current cpu scheduler is best for 2.6 rather than any gutting and
replacement of the interactivity estimator (which even though this scheme is
simple and easy to understand, it clearly is an example of). Given that we
have a "2.6 forever" policy, it also means any significant cpu scheduler
rewrite, even just of the interactivity estimator, is nigh on impossible to
implement.
Cheers,
Con
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/