All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: okorpil@fh-landshut.de
Cc: arun@ossi.co.in,
	linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Context Switch in Real Time  Linux Vs VxWorks (or any other RTOS)
Date: Fri, 16 Jul 2004 09:09:58 -0600	[thread overview]
Message-ID: <1089990598.22193.6417.camel@hermes> (raw)
In-Reply-To: <40F77AA3.8030703@fh-landshut.de>


On Fri, 2004-07-16 at 00:50, Oliver Korpilla wrote:
> 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.

Thanks for the plug :-)  [n.b. I am one of the main eCos developers]
FYI, look to http://sources.redhat.com/ecos for details.

>
> Be warned: Not all PowerPC processors are supported in eCos (last time I
> checked 74xx and 7xx were missing).

Ah, but they are simple to add (and have been, but not necessarily
public) as they are effectively PPC60x processors with some differences.

--
Gary Thomas <gary@mlbassoc.com>
MLB Associates


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-16 15:09 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 [this message]
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=1089990598.22193.6417.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=arun@ossi.co.in \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=okorpil@fh-landshut.de \
    /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.