[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1173684174.6659.13.camel@Homer.simpson.net>
Date: Mon, 12 Mar 2007 08:22:54 +0100
From: Mike Galbraith <efault@....de>
To: Ingo Molnar <mingo@...e.hu>
Cc: Con Kolivas <kernel@...ivas.org>,
linux kernel mailing list <linux-kernel@...r.kernel.org>,
ck list <ck@....kolivas.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2
On Sun, 2007-03-11 at 13:10 +0100, Ingo Molnar wrote:
> * Mike Galbraith <efault@....de> wrote:
>
> > > Full patch for 2.6.21-rc3-mm2:
> > > http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc3-mm2-rsdl-0.29.patch
> >
> > I'm seeing a cpu distribution problem running this on my P4 box.
>
> > With 2.6.21-rc3, X/Gforce maintain their ~50% cpu (remain smooth), and
> > the encoders (100%cpu bound) get whats left when Amarok isn't eating
> > it.
> >
> > I plunked the above patch into plain 2.6.21-rc3 and retested to
> > eliminate other mm tree differences, and it's repeatable. The nice 5
> > cpu hogs always receive considerably more that the nice 0 sleepers.
>
> hm. Do you get the same same problem on UP too? (i.e. lets eliminate any
> SMP/HT artifacts)
Behavior is slightly different with a UP kernel. Neither encoder
receives more cpu than X, but they each still receive more than gforce.
The distribution of X/Gforce vs lame/lame averages per eyeball to
roughly ~50:50.
I noticed Con posted an accounting fix, and applied it. No change.
-Mike
-
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