linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Ji <hji@netscreen.com>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-mm@kvack.org'" <linux-mm@kvack.org>
Subject: Thoughts about RTCore and RTLinux
Date: Thu, 4 Mar 2004 08:48:10 -0800	[thread overview]
Message-ID: <017B1BB60535DF4285666089FA048AC2A2E45B@SONOMA.netscreen.com> (raw)

Hi, folks,

I happen to read some white papers related to RTLinux. Below is some of
my personal thoughts/questions. 

* RTLinux's so called realtime extension-RTCORE  **was* to address the
previous issue--Linux is not realtime supported, for example, fully
kernel-preemptive; posix realtime extension. 

* After linux 2.6, I did not see any outstanding reason that people
still need to use a RTLinux **patch** to achieve realtime applications.
I mean, why not just linux itself? Not needed RTCORE anymore.

* From os/kernel viewpoint, it is very hard for me to position RTCORE,
but a realtime patch. I mean, RTCORE is not able to be identified into any
well-known os architecture. 

* If there is a very high performance micro-kernel, say, L4 or
QNX/Neutrino, I personally think it is much better than the RTCORE stuff,
which HAVE TO bind a secondary os as running time environment.

Some personal thoughts,
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

                 reply	other threads:[~2004-03-04 16:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=017B1BB60535DF4285666089FA048AC2A2E45B@SONOMA.netscreen.com \
    --to=hji@netscreen.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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