mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wessel Dankers <wsl@fruit.eu.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Scheduler priorities
Date: Thu, 28 Mar 2002 08:08:55 +0100	[thread overview]
Message-ID: <20020328070855.GB514@fruit.eu.org> (raw)
In-Reply-To: <20020327125828.U2343-100000@angelina.sl.pt> <1017236512.16546.116.camel@phantasy> <20020327202335.GA514@fruit.eu.org> <1017263732.17510.204.camel@phantasy>

On 2002-03-27 16:14:55-0500, Robert Love wrote:
> On Wed, 2002-03-27 at 15:23, Wessel Dankers wrote:
> 
> > Any plans for a SCHED_IDLE?
> 
> I think Ingo Molnar has mentioned lately doing one.
> 
> The problem is, it is not easy to implement right - there are priority
> inversion issues to deal with ...

Well evidently it should be root-only, just like SCHED_RR and SCHED_FIFO.
If the priority inversion issues are worked out this restriction could be
removed. I remember discussing this problem with Rik van Riel.
The kernel-preempt patch seems to be able to detect when a process holds a
lock; perhaps the process scheduler can temporarily revert to SCHED_NORMAL
when this is the case? Preferably with a large nice value.

--
Wessel Dankers <wsl@fruit.eu.org>

(the armchair engineer)

  reply	other threads:[~2002-03-28  7:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26 11:41 Nuno Miguel Rodrigues
2002-03-26 17:55 ` Mike Fedyk
2002-03-27  9:41   ` Frank Schaefer
2002-03-27 13:06     ` Nuno Miguel Rodrigues
2002-03-27 13:41       ` Robert Love
2002-03-27 20:23         ` Wessel Dankers
2002-03-27 21:14           ` Robert Love
2002-03-28  7:08             ` Wessel Dankers [this message]
2002-03-28  7:29               ` Robert Love
2002-03-29 21:42                 ` Pavel Machek
2002-03-29 23:52                   ` Robert Love

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=20020328070855.GB514@fruit.eu.org \
    --to=wsl@fruit.eu.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®