All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: Zan Lynx <zlynx@acm.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8-rc2-mm2, staircase sched and ESD
Date: Thu, 05 Aug 2004 11:42:36 +1000	[thread overview]
Message-ID: <4111908C.5070903@yahoo.com.au> (raw)
In-Reply-To: <cone.1091658687.786019.9775.502@pc.kolivas.org>

Con Kolivas wrote:

> Zan Lynx writes:
>
>> The 2.6.8-rc2-mm2 kernel has the staircase scheduler, right?  Well, I am
>> seeing an odd thing.  At least, I think it is odd.
>>
>> I'm running Fedora Core 2 and playing music with Rhythmbox.  When I
>> watch top sorted by priority, I see esd slowly increase its priority
>> until it reaches 38, then it goes back to 20.  ESD is only using 1-2%
>> CPU.
>>
>> This is causing a problem because doing just about anything in X, like
>> bring up a new window or drag a window causes the sound to just stop.
>>
>> Why does ESD's priority keep climbing?
>>
>> Oh yes, this does not happen if I change /proc/sys/fs/interactive to 
>> 0. When it is 0, X's priority climbs faster than ESDs and does not cause
>> the problem.
>
>
> Yes this is a known issue with esd. It basically wakes up far too 
> frequently for it's own good. esd should not be required with alsa 
> drivers and 2.6 since alsa supports sharing of the sound card / mixing 
> on it's own so adding esd adds an unnecessary layer to the sound 
> drivers. It ends up doing this:
> esd->oss emulation->alsa.
>

Even so, this would be a showstopper if we're talking about replacing 
the 2.6 scheduler,
wouldn't you agree?


  reply	other threads:[~2004-08-05  1:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 21:44 2.6.8-rc2-mm2, staircase sched and ESD Zan Lynx
2004-08-04 22:31 ` Con Kolivas
2004-08-05  1:42   ` Nick Piggin [this message]
2004-08-10 21:08   ` Martin Schlemmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4111908C.5070903@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zlynx@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.