public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: "sandeep lahane" <sandeep.lahane@gmail.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: Thu, 5 Apr 2007 15:53:16 +0530	[thread overview]
Message-ID: <2d51cbf80704050323u48bcb2f1u4861c3ff8a3eebe1@mail.gmail.com> (raw)
In-Reply-To: <f68850780704050311qe9ca888tec4c255c6c1a0b3e@mail.gmail.com>

On 4/5/07, Raseel Bhagat <raseelbhagat@gmail.com> wrote:
> Hi Sandeep,
>
> On 4/5/07, sandeep lahane <sandeep.lahane@gmail.com> wrote:
>
> >They have a paravirtualization based approach using which
> > guest OSes like RTOS or other rich OSes can be run simultaneously on
> > an embedded platform. These guest OSes can communicate using inter OS
> > communication mechanisms. They are partitioning resources which can be
> > partitioned like system RAM and resources like CPU, MMU and interrupt
> > controller are virtualized since they can't be partitioned. So
> > basically, what they are doing is almost totally irrelevant with this
> > question, since they are not trying to make Linux a RTOS, rather they
> > are making Linux and other guest OSes co-exist with RTOSes
> > simultaneously. Please CMIIW.
> >
>
> I completely concur with you. And it makes lot of sense too.
> For example RTLinux (Real time Linux) from FSMLabs is another such approach.
> They have a micro-kernel , which is basically a core real tie\me
> kernel, which sits on top of the vanilla linux kernel. This way, all
> the real time tasks are handled by the Microkernel during whcih time
> Linux kernel runs as an idle process. Only when no RT tasks are
> present, the vanilla Linux kernel executes all the non-RT tasks.
> This way, RT behaviour is accomplished without having to modify the
> core Linux kernel.
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>

Yes, may be the poster is looking for RTLinux kind of thing.
-- 

Regards,
Sandeep.
-
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-05 10:23 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 [this message]
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=2d51cbf80704050323u48bcb2f1u4861c3ff8a3eebe1@mail.gmail.com \
    --to=sandeep.lahane@gmail.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