From: Mike Galbraith <efault@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: Re: patch O1int for 2.5.73 - interactivity work
Date: Wed, 25 Jun 2003 21:00:26 +0200 [thread overview]
Message-ID: <5.2.0.9.2.20030625204242.00ceda90@pop.gmx.net> (raw)
In-Reply-To: <200306260209.45020.kernel@kolivas.org>
At 02:09 AM 6/26/2003 +1000, Con Kolivas wrote:
>I'm still working on something for the "xmms stalls if started during very
>heavy load" as a different corner case.
One way to deal with that problem would be to create a very high priority
queue which is reserved for very light weight tasks, and heavily protected
against them going cpu hungry. If a forking task has a run history worthy
of trial, slip it straight into the high priority queue... and be prepared
to beat it into submission should it misbehave (short term run_avg ever
exceeds X, you're outta here buddy, and if this queue is consuming more
than Y, sorry, we're closed).
Another way would be to factor task age into the priority calculation, with
age becoming rapidly less important. Xmms' audio threads are light weight,
and will quickly be able to sustain their priority. Others would
(hopefully) rapidly fall down where they belong.
Just a couple random thoughts, both of which I can see problems with ;-)
-Mike
next prev parent reply other threads:[~2003-06-25 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 16:09 Con Kolivas
2003-06-25 19:00 ` Mike Galbraith [this message]
2003-06-25 19:34 ` Daniel Gryniewicz
2003-06-25 20:33 ` Mike Galbraith
2003-06-25 21:43 ` Con Kolivas
2003-06-25 21:53 ` Felipe Alfaro Solana
2003-06-25 23:10 ` Andy Pfiffer
2003-06-25 23:39 ` Con Kolivas
2003-06-26 20:16 ` Diego Calleja García
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=5.2.0.9.2.20030625204242.00ceda90@pop.gmx.net \
--to=efault@gmx.de \
--cc=felipe_alfaro@linuxmail.org \
--cc=kernel@kolivas.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
all inboxes | Powered by JetHome®