From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] SCHED_SOFTRR starve-free linux scheduling policy ...
Date: Sun, 10 Aug 2003 02:19:56 -0700 [thread overview]
Message-ID: <20030810091956.GB12746@pegasys.ws> (raw)
In-Reply-To: <5.2.1.1.2.20030810101700.019bc528@pop.gmx.net>
On Sun, Aug 10, 2003 at 10:18:43AM +0200, Mike Galbraith wrote:
> At 05:56 PM 8/10/2003 +1000, Nick Piggin wrote:
>
>
> >Mike Galbraith wrote:
> >
> >>At 03:43 PM 8/10/2003 +1000, Nick Piggin wrote:
> >>
> >>
> >>>Roger Larsson wrote:
> >>>
> >>>>* SCHED_FIFO requests from non root should also be treated as
> >>>>SCHED_SOFTRR
> >>>
> >>>I hope computers don't one day become so fast that SCHED_SOFTRR is
> >>>required for skipless mp3 decoding, but if they do, then I think
> >>>SCHED_SOFTRR should drop its weird polymorphing semantics ;)
> >>
> >>
> >>:) My box is slow enough to handle them just fine, as long as I make
> >>sure that oinkers don't share the same queue with the light weight player.
> >
> >
> >Just my (unsuccessful) attempt at humor!
>
> (was successful here... made for wide grin:)
Here too.
You know, that SCHED_SOFTRR is almost sounding like it
should be a SCHED_RESERVED where you could specify a
quantity of CPU time reserved for each task in
SCHED_RESERVED individually rather like isochronous which
was brought up earlier by Con. Of course you'd have to make
sure some time was unreservable.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2003-08-10 9:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.55.0307131442470.15022@bigblue.dev.mcafeelabs.c om>
2003-07-14 7:11 ` [patch] SCHED_SOFTRR starve-free linux scheduling policy Mike Galbraith
2003-07-13 21:51 ` Davide Libenzi
2003-08-09 14:05 ` Daniel Phillips
2003-08-09 17:47 ` Mike Galbraith
2003-08-09 23:58 ` Daniel Phillips
2003-08-10 6:06 ` Mike Galbraith
2003-08-10 0:41 ` Daniel Phillips
2003-08-10 6:41 ` Mike Galbraith
2003-08-10 15:46 ` Daniel Phillips
2003-08-10 17:49 ` Mike Galbraith
2003-08-10 20:28 ` Daniel Phillips
2003-08-11 5:31 ` Mike Galbraith
2003-08-11 13:54 ` Takashi Iwai
2003-08-10 2:05 ` Roger Larsson
2003-08-10 5:43 ` Nick Piggin
2003-08-10 7:41 ` Mike Galbraith
2003-08-10 7:56 ` Nick Piggin
2003-08-10 8:18 ` Mike Galbraith
2003-08-10 9:19 ` jw schultz [this message]
2003-08-11 17:01 ` Roger Larsson
2003-08-11 17:25 ` Takashi Iwai
[not found] ` <200308100405.52858.roger.larsson@skelleftea.mail.telia.com >
2003-08-10 7:11 ` Mike Galbraith
2003-08-12 7:23 ` Rob Landley
2003-08-12 23:35 ` Pavel Machek
2003-08-13 6:26 ` Mike Galbraith
2003-08-13 9:41 ` Pavel Machek
2003-07-14 7:12 ` Davide Libenzi
2003-07-14 7:24 ` Jamie Lokier
2003-07-14 7:35 ` Davide Libenzi
2003-07-14 9:11 ` Mike Galbraith
[not found] ` <Pine.LNX.4.55.0307140004390.3435@bigblue.dev.mcafeelabs.co m>
2003-07-14 8:14 ` Mike Galbraith
2003-07-14 15:09 ` Davide Libenzi
[not found] ` <Pine.LNX.4.55.0307140805220.4371@bigblue.dev.mcafeelabs.co m>
2003-07-14 16:06 ` Mike Galbraith
2003-07-14 17:22 ` Davide Libenzi
[not found] ` <Pine.LNX.4.55.0307141015010.4828@bigblue.dev.mcafeelabs.co m>
2003-07-15 4:56 ` Mike Galbraith
2003-07-15 15:47 ` Davide Libenzi
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=20030810091956.GB12746@pegasys.ws \
--to=jw@pegasys.ws \
--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;
as well as URLs for NNTP newsgroup(s).