From: Oliver Korpilla <okorpil@fh-landshut.de>
To: arun@ossi.co.in
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Context Switch in Real Time Linux Vs VxWorks (or any other RTOS)
Date: Fri, 16 Jul 2004 08:50:11 +0200 [thread overview]
Message-ID: <40F77AA3.8030703@fh-landshut.de> (raw)
In-Reply-To: <000001c46af2$642f7c40$e100a8c0@arunprasad>
Arun Prasad Velu wrote:
>
>I am in the process of analyzing the feasibility of migrating an
>existing VxWorks system (MPC860 target) to Linux (RTOS).
>
>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.
I hardly guess context switching will be your main problem, because the
stock Linux kernel does not support hard realtime!
You either have to use RTAI (free kernel modification that requires
drivers to be rewritten for realtime), RTLinux (nearly the same,
non-free, patented) or modified Linux kernels from TimeSys or MontaVista
(who both add real-time capabilities in a more stock-Linux-compliant way).
Depending on your target, eCos (a free embedded operating system with a
focus on minimal code) may be the better choice for you, especially if
your platform is already supported.
Be warned: Not all PowerPC processors are supported in eCos (last time I
checked 74xx and 7xx were missing).
With kind regards,
Oliver Korpilla
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-16 6:50 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 [this message]
2004-07-16 15:09 ` Gary Thomas
2004-07-16 12:12 ` Kevin P. Dankwardt
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=40F77AA3.8030703@fh-landshut.de \
--to=okorpil@fh-landshut.de \
--cc=arun@ossi.co.in \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.