From: Lee Revell <rlrevell@joe-job.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
Con Kolivas <kernel@kolivas.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
ankitjain1580@yahoo.com, Ingo Molnar <mingo@elte.hu>,
rml@tech9.net
Subject: Re: Difference in priority
Date: Wed, 13 Oct 2004 01:39:39 -0400 [thread overview]
Message-ID: <1097645978.5879.4.camel@krustophenia.net> (raw)
In-Reply-To: <416CB85A.7030309@osdl.org>
On Wed, 2004-10-13 at 01:08, Randy.Dunlap wrote:
> Lee Revell wrote:
> > On Tue, 2004-10-12 at 21:17, Albert Cahalan wrote:
> >
> >>I can't see why the RT priority range would be increased.
> >>It's overkill already, especially since Linux doesn't have
> >>priority inheritance. Since POSIX requires 32 levels, that
> >>is the right number. Actually using more than one level
> >>(remember: NO priority inheritance) might not be wise.
> >
> >
> > Linux will probably have priority inheritance soon. See the "Real Time
> > Kernel" thread.
>
> Is that opinion based any on this article and Linus's comments in it?
>
> http://news.com.com/A+new+direction+for+Linux+for+gadgets/2100-7344_3-5406291.html?tag=cd.top
>
No, but priority inheritance is not the same as making Linux an RTOS.
Lee
next prev parent reply other threads:[~2004-10-13 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 0:57 Difference in priority Albert Cahalan
2004-10-13 0:15 ` Con Kolivas
2004-10-13 1:17 ` Albert Cahalan
2004-10-13 1:26 ` Con Kolivas
2004-10-13 4:58 ` Lee Revell
2004-10-13 5:08 ` Randy.Dunlap
2004-10-13 5:39 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 12:17 Ankit Jain
2004-10-11 12:35 ` Con Kolivas
2004-10-11 12:43 ` Con Kolivas
2004-10-12 9:28 ` Ankit Jain
2004-10-12 10:40 ` Con Kolivas
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=1097645978.5879.4.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=albert@users.sourceforge.net \
--cc=ankitjain1580@yahoo.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rddunlap@osdl.org \
--cc=rml@tech9.net \
/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