[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200703170813.32594.kernel@kolivas.org>
Date: Sat, 17 Mar 2007 08:13:31 +1100
From: Con Kolivas <kernel@...ivas.org>
To: Mike Galbraith <efault@....de>
Cc: ck@....kolivas.org, Ingo Molnar <mingo@...e.hu>,
Al Boldi <a1426z@...ab.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: RSDL v0.31
On Saturday 17 March 2007 02:34, Mike Galbraith wrote:
> On Sat, 2007-03-17 at 00:40 +1100, Con Kolivas wrote:
> > Here are full patches for rsdl 0.31 for various base kernels. A full
> > announce with a fresh -mm series will follow...
> >
> > http://ck.kolivas.org/patches/staircase-deadline/2.6.20.3-rsdl-0.31.patch
> > http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc3-sched-rsdl-0.
> >31.patch
> > http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc3-mm2-rsdl-0.31
> >.patch
>
> It still has trouble with the x/gforce vs two niced encoders scenario.
> The previously reported choppiness is still present.
>
> I suspect that x/gforce landing in the expired array is the trouble, and
> that this will never be smooth without some kind of exemption. I added
> some targeted unfairness to .30, and it didn't help much at all.
>
> Priorities going all the way to 1 were a surprise.
It wasn't going to change that case without renicing X. I said that from the
start to maintain fairness it's the only way to keep a fair design, and give
more cpu to X. The major difference in this one is the ability to run
different nice values without killing the latency of the relatively niced
ones.
--
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists