From: William Lee Irwin III <wli@holomorphy.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
davidm@hpl.hp.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: O(1) scheduler starvation
Date: Wed, 18 Jun 2003 09:52:27 -0700 [thread overview]
Message-ID: <20030618165227.GK26348@holomorphy.com> (raw)
In-Reply-To: <5.2.0.9.2.20030618113653.0277d780@pop.gmx.net>
On Wed, Jun 18, 2003 at 02:04:45PM +0200, Mike Galbraith wrote:
> I've got thud licked (without the restricting sleep to time_slice),
> test-starve works right as well, and interactivity is up. Tasks waking
> each other in a loop is a bitch and a half though, and need to be beaten
> about the head and shoulders. Going to a synchronous wakeup for pipes
> (talking stock kernel now) cures irman process_load's ability to starve...
> IFF you're running it from a vt. If you're in an xterm, it'll still climb
> up from the bottom (only place where it can't starve anybody) and starve
> via pass-the-baton wakeup DoS. That will/does take the joy out of using
> xmms. If xmms didn't use multiple threads, it'd be much worse... right
> now, you'll lose eye-candy [cpu hungry visualization stuff] before you lose
> sound [at next song].
That's great. I'd love to see the patch.
-- wli
next prev parent reply other threads:[~2003-06-18 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 7:53 O(1) scheduler starvation Felipe Alfaro Solana
2003-06-18 12:04 ` Mike Galbraith
2003-06-18 12:16 ` Helge Hafting
2003-06-18 12:32 ` Mike Galbraith
2003-06-18 14:22 ` Felipe Alfaro Solana
2003-06-18 15:54 ` Mike Galbraith
2003-06-18 15:59 ` Con Kolivas
2003-06-18 16:29 ` Mike Galbraith
2003-06-18 21:30 ` Felipe Alfaro Solana
2003-06-18 22:32 ` Mike Galbraith
2003-06-18 16:52 ` William Lee Irwin III [this message]
2003-06-18 17:17 ` Mike Galbraith
2003-06-18 16:51 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 20:44 Ricardo Galli
2003-06-18 20:48 ` Marc-Christian Petersen
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=20030618165227.GK26348@holomorphy.com \
--to=wli@holomorphy.com \
--cc=davidm@hpl.hp.com \
--cc=efault@gmx.de \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox