mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oswald Buddenhagen <ob6@inf.tu-dresden.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: static scheduling - SCHED_IDLE?
Date: Wed, 7 Mar 2001 20:20:27 +0100	[thread overview]
Message-ID: <20010307202027.B27421@ugly.wh8.tu-dresden.de> (raw)
In-Reply-To: <20010307184000.A26594@ugly.wh8.tu-dresden.de> <Pine.LNX.4.33.0103071447340.1409-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33.0103071447340.1409-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Wed, Mar 07, 2001 at 03:04:00PM -0300

> The problem with these things it that sometimes such a task may hold
> a lock, which can prevent higher-priority tasks from running.
> 
true ... three ideas:
- a sort of temporary priority elevation (the opposite of SCHED_YIELD)
  as long as the process holds some lock
- automatically schedule the task, if some higher-priorized task wants
  the lock
- preventing the processes from aquiring locks at all (obviously this
  is not possible for required locks inside the kernel, but i don't
  know enough about this)

> A solution would be to make sure that these tasks get at least one
> time slice every 3 seconds or so, so they can release any locks
> they might be holding and the system as a whole won't livelock.
> 
did "these" apply only to the tasks, that actually hold a lock?
if not, then i don't like this idea, as it gives the processes
time for the only reason, that it _might_ hold a lock. this basically 
undermines the idea of static classes. in this case, we could actually
just make the "nice" scale incredibly large and possibly nonlinear, 
as mark suggested.

best regards

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Nothing is fool-proof to a sufficiently talented fool.

  reply	other threads:[~2001-03-07 19:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 17:40 Oswald Buddenhagen
2001-03-07 18:04 ` Rik van Riel
2001-03-07 19:20   ` Oswald Buddenhagen [this message]
2001-03-07 21:34     ` ludovic
2001-03-08 11:17       ` Zdenek Kabelac
2001-03-08 11:41         ` Andrew Morton
2001-03-08 13:29     ` Boris Dragovic
2001-03-08 13:44       ` Rik van Riel
2001-03-08 20:19         ` Boris Dragovic
2001-03-08 20:47           ` Rik van Riel
2001-03-09 19:38             ` george anzinger
2001-03-09 20:19               ` Adrian Cox
2001-03-12 18:05                 ` Jamie Lokier
2001-03-12 19:37                   ` Adrian Cox
2001-03-13  9:40                     ` Jamie Lokier
2001-03-10  2:58               ` Rik van Riel
2001-03-09 19:42             ` Jamie Lokier
2001-03-10  3:02               ` Rik van Riel
2001-03-09 20:09                 ` Jamie Lokier
2001-03-10  4:56                   ` Rik van Riel
2001-03-14 13:19                     ` Jamie Lokier
2001-03-15  3:13                       ` Rik van Riel
2001-03-14 14:26                   ` Philipp Rumpf
2001-03-09 11:26       ` Pavel Machek

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=20010307202027.B27421@ugly.wh8.tu-dresden.de \
    --to=ob6@inf.tu-dresden.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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®