From: Rodrigo Rubira Branco <rrbranco@br.ibm.com>
To: Raseel Bhagat <raseelbhagat@gmail.com>
Cc: kernelnewbies@nl.linux.org, linux-newbie@vger.kernel.org
Subject: Re: Why is Linux not RTOS?
Date: Tue, 29 May 2007 21:47:35 -0300 [thread overview]
Message-ID: <1180486056.5473.28.camel@localhost.localdomain> (raw)
In-Reply-To: <f68850780704050307o3639b8bbi993e6a7a11adbe72@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
Ok, let's clarify somethings ;)
First of all I really recommend this links:
http://www.linuxjournal.com/article/9361
http://rt.wiki.kernel.org/
The real-time implementations previously commented in the list relies on
"interrupt shielding" (forcing interrupts to run on a reserved CPU) and
"CPU pinning" (forcing real-time tasks to only run on a CPU which
doesn't run any other tasks), so we can't say it's a 'real' real-time ;)
(it does not take the best advantage of multiple cpu's for example and
needs more than just one in anyway).
Legal notice: It's just my personal contribution.
P.S.: Sorry my delay to answer that ;)
On Thu, 2007-04-05 at 15:37 +0530, Raseel Bhagat wrote:
> Hi Tzahi,
>
> On 4/5/07, Tzahi Fadida <Tzahi.ML2@gmail.com> wrote:
> > What is this i hear about PREEMT_RT from VirtualLogix:
> > http://www.wirelessiq.com/content/newsfeed/9867.html
>
> I think the author is trying to mention the different innovative
> solutions to the latency issue in the GPOS Linux Kernel. PREEMPT_RT ,
> IIRC was a Real Time patch by Ingo Molar.
> VirtualLogix's Virtual OS is another such solution, etc.
>
> Thanks,
> Raseel
> -
> 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
--
Rodrigo Rubira Branco
Software Engineer
Advanced Linux Response Team (ALRT) / Linux on Power Toolchain
IBM Linux Technology Center (IBM/LTC)
rrbranco@br.ibm.com
GPG KeyID: 1FCEDEA1
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-30 0:47 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
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 [this message]
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=1180486056.5473.28.camel@localhost.localdomain \
--to=rrbranco@br.ibm.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-newbie@vger.kernel.org \
--cc=raseelbhagat@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox