[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75b66ecd0704190722l5ba8db7n52734c209504e802@mail.gmail.com>
Date: Thu, 19 Apr 2007 10:22:39 -0400
From: "Lee Revell" <rlrevell@...-job.com>
To: "Peter Williams" <pwil3058@...pond.net.au>
Cc: "Con Kolivas" <kernel@...ivas.org>, "Ingo Molnar" <mingo@...e.hu>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Nick Piggin" <npiggin@...e.de>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Matt Mackall" <mpm@...enic.com>,
"William Lee Irwin III" <wli@...omorphy.com>,
"Mike Galbraith" <efault@....de>, "ck list" <ck@....kolivas.org>,
"Bill Huey" <billh@...ppy.monkey.org>,
linux-kernel@...r.kernel.org,
"Arjan van de Ven" <arjan@...radead.org>,
"Thomas Gleixner" <tglx@...utronix.de>
Subject: Re: Renice X for cpu schedulers
On 4/19/07, Peter Williams <pwil3058@...pond.net.au> wrote:
> PS I think that the tasks most likely to be adversely effected by X's
> CPU storms (enough to annoy the user) are audio streamers so when you're
> doing tests to determine the best nice value for X I suggest that would
> be a good criterion. Video streamers are also susceptible but glitches
> in video don't seem to annoy users as much as audio ones.
IMHO audio streamers should use SCHED_FIFO thread for time critical
work. I think it's insane to expect the scheduler to figure out that
these processes need low latency when they can just be explicit about
it. "Professional" audio software does it already, on Linux as well
as other OS...
Lee
-
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