From: "Kevin P. Dankwardt" <k@kcomputing.com>
To: <arun@ossi.co.in>, <penguinppc-team@lists.penguinppc.org>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Context Switch in Real Time Linux Vs VxWorks (or any other RTOS)
Date: Fri, 16 Jul 2004 07:12:59 -0500 [thread overview]
Message-ID: <KCEOLLHGFJIAFNAMGACHIECKDPAA.k@kcomputing.com> (raw)
In-Reply-To: <000001c46af2$642f7c40$e100a8c0@arunprasad>
There are a number of approaches to real-time in Linux. There are also
several different task/thread/process models from which to choose. Some
involve kernel space and some allow for user space. Some are open source and
some are proprietary. One has to decide on a number of factors before
choosing the solution best suited.
If you are comfortable with the flat memory model of VxWorks then a kernel
space solution may be acceptable. Kernel space solutions such as RTAI have
quite low "context switch" and quite fast interrupt response time.
For more information I'd recommend starting by reading (my) articles from
Embedded Linux Journal:
http://www.linuxdevices.com/articles/AT5997007602.html
http://www.linuxdevices.com/articles/AT5503476267.html
http://www.linuxdevices.com/articles/AT6320079446.html
Best of luck,
Kevin Dankwardt
>I'd like to compare the features of Linux and VxWorks with respect to the
>Real Time capabilities. I am little concerned about Linux's Context
>Switching.
>I'd like to get your opinion on this. Even if I want to move to Linux, I'll
>have to convince my management. So, any pointers on comparison of Linux Vs
>VxWorks with respect to Real Time capabilities would be highly appreciated.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-07-16 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NIBBKGBHPKFDFAOHCGBLIECICAAA.arun@ossi.co.in>
2004-07-16 5:04 ` Context Switch in Real Time Linux Vs VxWorks (or any other RTOS) Arun Prasad Velu
2004-07-16 6:50 ` Oliver Korpilla
2004-07-16 15:09 ` Gary Thomas
2004-07-16 12:12 ` Kevin P. Dankwardt [this message]
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=KCEOLLHGFJIAFNAMGACHIECKDPAA.k@kcomputing.com \
--to=k@kcomputing.com \
--cc=arun@ossi.co.in \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=penguinppc-team@lists.penguinppc.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;
as well as URLs for NNTP newsgroup(s).