public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Huey (Hui) <billh@gnuppy.monkey.org>
To: Ming Lei <lei.ming@attbi.com>
Cc: linux-kernel@vger.kernel.org,
	"Bill Huey (Hui)" <billh@gnuppy.monkey.org>
Subject: Re: linux rt priority  thread corrupt  global variable?
Date: Thu, 8 May 2003 02:52:38 -0700	[thread overview]
Message-ID: <20030508095238.GA20844@gnuppy.monkey.org> (raw)
In-Reply-To: <029601c31540$b57f1280$0305a8c0@arch.sel.sony.com>

On Thu, May 08, 2003 at 02:03:35AM -0700, Ming Lei wrote:
> Related questions:
> 
> Is linux kernel 2.4.10 considered strictly preemptive such as VxWorks or
> other RTOS? I guess 2.4.10 may simulate preemptive with running scheduler on
> every syscall or interrupt returns. Am I right?

No, it's not a fully preemptive kernel, but spreads preemption points
throughout the source tree, both directly and indirectly, instead. Spinlocks
are the primary mutex of choice in Linux and create atomic critical sections
that can't be preempted with respect to the normal Linux scheduler. Fully
preemptive systems tend to use sleepable locks with relaxed preemptability
within critical sections and add the possible option of priority inheritance
depending on the system.

If you're going to do RT Linux related stuff use RTLinux, RTAI or other
commerical options instead.

> Is printf() real-time priority thread safe?

Stock Linux is definitely not if I understand what you're saying and
if I understand the code correctly. :)

bill


  parent reply	other threads:[~2003-05-08  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08  9:03 linux rt priority thread corrupt global variable? Ming Lei
2003-05-08  9:43 ` Jörn Engel
2003-05-08 16:59   ` Ming Lei
2003-05-08  9:51 ` Arjan van de Ven
2003-05-08  9:52 ` Bill Huey [this message]
2003-05-08  9:59   ` Bill Huey
2003-05-08 10:42     ` Bill Huey
2003-05-08 20:45 ` Roger Larsson

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=20030508095238.GA20844@gnuppy.monkey.org \
    --to=billh@gnuppy.monkey.org \
    --cc=lei.ming@attbi.com \
    --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