[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c0942db0703200816r36544407o1f60270c5d1da7af@mail.gmail.com>
Date: Tue, 20 Mar 2007 08:16:54 -0700
From: "Ray Lee" <madrabbit@...il.com>
To: "Mark Lord" <lkml@....ca>
Cc: "Linus Torvalds" <torvalds@...ux-foundation.org>,
"Xavier Bestel" <xavier.bestel@...e.fr>,
"Al Boldi" <a1426z@...ab.com>, "Mike Galbraith" <efault@....de>,
"Con Kolivas" <kernel@...ivas.org>, ck@....kolivas.org,
"Serge Belyshev" <belyshev@...ni.sinp.msu.ru>,
"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org,
"Nicholas Miell" <nmiell@...cast.net>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: RSDL v0.31
On 3/20/07, Mark Lord <lkml@....ca> wrote:
> I've droppped it from my machine -- interactive response is much
> more important for my primary machine right now.
Help out with a data point? Are you running KDE as well? If you are,
then it looks like the common denominator that RSDL is handling poorly
is client-server communication. (KDE's KIO slaves in this case, but X
in general.)
If so, one would hope that a variation on Linus's 2.5.63 pipe wakeup
pass-the-interactivity idea could work here. The problem with that
original patch, IIRC, was that a couple of tasks could bounce their
interactivity bonus back and forth and thereby starve others. Which
might be expected given there was no 'decaying' of the interactivity
bonus, which means you can make a feedback loop.
Anyway, looks like processes that do A -> B -> A communication chains
are getting penalized under RSDL. In which case, perhaps I can make a
test case that exhibits the problem without having to have the same
graphics card or desktop as you.
Ray
-
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