From: Mike Fedyk <mfedyk@matchmail.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Nick Piggin <piggin@cyberone.com.au>,
John Yau <jyau_kernel_dev@hotmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Priority Inversion in Scheduling
Date: Tue, 9 Sep 2003 22:35:49 -0700 [thread overview]
Message-ID: <20030910053549.GE28279@matchmail.com> (raw)
In-Reply-To: <6.0.0.22.0.20030910062610.01cfacd8@pop.gmx.net>
On Wed, Sep 10, 2003 at 06:42:10AM +0200, Mike Galbraith wrote:
> At 02:23 AM 9/10/2003, Nick Piggin wrote:
> >Hi John,
> >Your mechanism is basically "backboost". Its how you get X to keep a
> >high piroirity, but quite unpredictable. Giving a boost to a process
> >holding a semaphore is an interesting idea, but it doesn't address the
> >X problem.
>
> FWIW, I tried the hardware usage bonus thing, and it does cure the X
> inversion problem (yeah, it's a pretty cheezy way to do it). It also
> cures xmms skips if you can't get to the top without hw usage. I also
> tried a cpu limited backboost from/to tasks associated with hardware, and
> it hasn't run amok... yet ;-)
Against which scheduler, and when are you going to post the patch?
next prev parent reply other threads:[~2003-09-10 5:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 19:57 Priority Inversion in Scheduling John Yau
2003-09-10 0:23 ` Nick Piggin
2003-09-10 4:42 ` Mike Galbraith
2003-09-10 5:35 ` Mike Fedyk [this message]
2003-09-10 6:22 ` Mike Galbraith
2003-09-10 9:28 ` Nick Piggin
2003-09-10 10:47 ` Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2003-09-10 2:20 John Yau
2003-09-10 2:31 ` Nick Piggin
2003-09-10 5:41 ` Priority Inversion in Scheduling John Yau
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=20030910053549.GE28279@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=efault@gmx.de \
--cc=jyau_kernel_dev@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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.