public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
Cc: linux-kernel@vger.kernel.org, Davide Libenzi <davidel@xmailserver.org>
Subject: Re: [patch] SCHED_SOFTRR starve-free linux scheduling policy  ...
Date: Mon, 11 Aug 2003 19:25:49 +0200	[thread overview]
Message-ID: <s5h3cg8jeci.wl@alsa2.suse.de> (raw)
In-Reply-To: <200308111901.13131.roger.larsson@skelleftea.mail.telia.com>

At Mon, 11 Aug 2003 19:01:13 +0200,
Roger Larsson wrote:
> 
> On Sunday 10 August 2003 07.43, 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 ;)
> 
> After some tinking...
> 
> Neither SCHED_FIFO nor SCHED_RR should automatically be promoted to 
> SCHED_SOFTRR in the kernel.
> 
> * If a process knows about SCHED_SOFTRR it should use that.
>   (example: arts should use SCHED_SOFTRR not SCHED_FIFO)
>   Problem: what to do when compiling for UN*Xes that does not have SOFTRR.
>   [Is there any other UN*X that have something resembling of this? What do
>    they call it?]
> 
> * Cases where the code has not been modified should be handled by a wrapper
>   (library). setscheduler is a weak symbol isn't it?

i agree here.

i understand it's introduced for convenience, but the apps are anyway
to be modified to adapt SOFTRR with normal users in most cases
(e.g. checking the uid, etc)...


Takashi

  reply	other threads:[~2003-08-11 17:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-13 21:51 [patch] SCHED_SOFTRR starve-free linux scheduling policy 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
2003-08-11 17:01         ` Roger Larsson
2003-08-11 17:25           ` Takashi Iwai [this message]
     [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
     [not found] <Pine.LNX.4.55.0307131442470.15022@bigblue.dev.mcafeelabs.c om>
2003-07-14  7:11 ` Mike Galbraith
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=s5h3cg8jeci.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.larsson@skelleftea.mail.telia.com \
    /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