Linux Newbie help
 help / color / mirror / Atom feed
From: "Rick Brown" <rick.brown.3@gmail.com>
To: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>
Cc: linux-newbie@vger.kernel.org, kernelnewbies <kernelnewbies@nl.linux.org>
Subject: Re: Why is Linux not RTOS?
Date: Wed, 4 Apr 2007 18:35:23 +0530	[thread overview]
Message-ID: <7783925d0704040605s4590d421y39ae5b13a020a8a@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.0.83.0704040858070.28216@sigma.j-a-k-j.com>

On 4/4/07, John Anthony Kazos Jr. <jakj@j-a-k-j.com> wrote:
> > Why is Linux kernel considered a (hard) realtime OS? I already
> > understand the basic reason is that the linux kernel does not
> > guarantee that a task will be completed on time. But I would
> > appreciate answers in terms of more of kernel jargons.
> >
> > What stops us from classifying kernel as hard RTOS? Is it because at
> > times the kernel is non-preemptive (for e.g. while holding spinlocks)?
> > Has it got something to do with interrupt latency / scheduling latency
> > etc?
> >
> > Is the behaviour of the kernel (when it is preemptive) similar to hard
> > real time OS ??
>
> From what I've read, the preemption in the kernel is mostly a hack because
> nobody's found a way to reduce the latency of certain long functions yet.
>
> And there is a separate RTOS version called Real-Time Linux or RTL...I
> think. Try googling. It's used in life-support machinery and so forth.

Yes, I'm aware that there are quite a lot of different patches /
projects aimed at giving better RTOS behaviour ... but my question was
aimed at vanilla kernel.

Thanks,

Rick
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2007-04-04 13:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-04 12:21 Why is Linux not RTOS? Rick Brown
2007-04-04 13:00 ` John Anthony Kazos Jr.
2007-04-04 13:05   ` Rick Brown [this message]
2007-04-04 15:21     ` Daniel Cheng
2007-04-05  9:36       ` Tzahi Fadida
2007-04-05 10:05         ` sandeep lahane
2007-04-05 10:11           ` Raseel Bhagat
2007-04-05 10:23             ` sandeep lahane
2007-04-05 13:28               ` Mark Hounschell
2007-04-05 10:07         ` Raseel Bhagat
2007-05-30  0:47           ` Rodrigo Rubira Branco
2007-05-31  1:16             ` K.R. Foley
2007-04-05  7:14 ` Pradeep
2007-04-05  9:01   ` Raseel Bhagat
2007-04-05  9:05     ` Pharaoh .
2007-04-05 11:52 ` Not Initialize the shrinker->list after kmalloc() in mm/vmscan.c(V2.6.12)? qingxiaoming
2007-04-09  5:57   ` Rajat Jain

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=7783925d0704040605s4590d421y39ae5b13a020a8a@mail.gmail.com \
    --to=rick.brown.3@gmail.com \
    --cc=jakj@j-a-k-j.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-newbie@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