From: Andrew Morton <andrewm@uow.edu.au>
To: Zdenek Kabelac <kabi@i.am>
Cc: ludovic <ludovic.fernandez@sun.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: static scheduling - SCHED_IDLE?
Date: Thu, 08 Mar 2001 22:41:41 +1100 [thread overview]
Message-ID: <3AA76FF5.987E8F2F@uow.edu.au> (raw)
In-Reply-To: <3AA6A97A.1EDE6A0B@sun.com> <3AA76A53.CEC1B234@i.am>
Zdenek Kabelac wrote:
>
> > Since the linux kernel is not preemptive, the problem is a little
> > bit more complicated; A low priority kernel thread won't lose the
> > CPU while holding a lock except if it wants to. That simplifies the
> > locking problem you mention but the idea of background low priority
> > threads that run when the machine is really idle is also not this
> > simple.
>
> You seem to have a sence for black humor right :) ?
> As this is purely a complete nonsence
> - you were talking about M$Win3.11 right ?
> (are you really the employ of Sun ??)
awww.. Don't say that. Ludovic is a nice guy.
Look. Suppose you have a SCHED_IDLE task which does this,
in the kernel:
down(&sem1);
down(&sem2); /* This sleeps */
Now, a SCHED_OTHER task does this, in user space:
for ( ; ; )
;
We're dead. The SCHED_IDLE task will never be scheduled,
and hence will never release sem1. The solution to this
problem is well known but, as Ludovic says, "not simple".
-
next prev parent reply other threads:[~2001-03-08 11:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 17:40 static scheduling - SCHED_IDLE? Oswald Buddenhagen
2001-03-07 18:04 ` Rik van Riel
2001-03-07 19:20 ` Oswald Buddenhagen
2001-03-07 21:34 ` ludovic
2001-03-08 11:17 ` Zdenek Kabelac
2001-03-08 11:41 ` Andrew Morton [this message]
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=3AA76FF5.987E8F2F@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=kabi@i.am \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.fernandez@sun.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.