mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bill Huey (hui) <bhuey@lnxw.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: karim@opersys.com, Scott Wood <scott@timesys.com>,
	Ingo Molnar <mingo@elte.hu>,
	"La Monte H.P. Yarroll" <piggy@timesys.com>,
	Manas Saksena <manas.saksena@timesys.com>,
	Philippe Gerum <rpm@xenomai.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] IRQ threads
Date: Wed, 28 Jul 2004 13:21:07 -0700	[thread overview]
Message-ID: <20040728202107.GA6952@nietzsche.lynx.com> (raw)
In-Reply-To: <1091043218.766.10.camel@mindpipe>

On Wed, Jul 28, 2004 at 03:33:38PM -0400, Lee Revell wrote:
> I am familiar with Adeos, as well as other hard-RT solutions for Linux. 
> I did my homework before deciding that I do not in fact need hard-RT, so
> I really am not interested in your flamewars, keep them on your RT
> mailing lists.
> 
> The part that was obvious commercially motivated FUD (and which you
> omitted) t in which you badmouth TimeSys and its services, then  Your
> .sig states that you are a consultant specializing in realtime and
> embedded Linux.

With that said, there's really two camps that are emerging in the real
time Linux field, dual and single kernel. The single kernel work that's
current being done could very well get Linux to being hard RT, assuming
that you solve all of the technical problems with things like RCU,
etc... in 2.6.

The dual kernels folks would be in less of position to VAR their own
stuff and sell proprietary products if Linux were to get native hard RT
performance if you accept that economic criteria. Who knows what the
actual results will be.

It could be that all of this work with Linux could bury prioprietary
OS product (such as LynxOS here) or it could open doors to other things
unknown things that were never possible previous to Linux getting some
kind of hard RT capability. It's certainly a scary notion to think about
with many variables to consider. Linux getting hard RT is inevitable.
It's just a question of how it'll be handled by proprietary OS vendors,
witness IBM for a positive example. A negative one would be Sun.

Now that Windriver System (the idiot folks that never understood Linux
before laying off tons of folks and disbanned the rather famous BSD/OS
group which I was apart of, etc...) and Red Hat is in the picture, it's
all starting to cook up.

All things to think about.

bill


  parent reply	other threads:[~2004-07-28 20:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 22:50 Scott Wood
2004-07-28  6:27 ` Ingo Molnar
2004-07-28 15:38   ` Karim Yaghmour
2004-07-28 16:01     ` Karim Yaghmour
2004-07-28 21:23   ` Bill Huey
2004-07-28 21:35     ` Scott Wood
2004-07-29 21:08       ` Bill Huey
2004-07-29 22:44       ` Ingo Molnar
2004-07-28 23:24   ` Scott Wood
2004-07-28  8:10 ` Ingo Molnar
2004-07-28 23:12   ` Scott Wood
2004-07-29 19:33     ` Ingo Molnar
2004-07-29 20:21       ` Scott Wood
2004-07-29 21:12         ` Alan Cox
2004-07-28 15:45 ` Karim Yaghmour
2004-07-28 18:28   ` Lee Revell
2004-07-28 19:12     ` Karim Yaghmour
2004-07-28 19:33       ` Lee Revell
2004-07-28 19:57         ` Karim Yaghmour
2004-07-28 20:35           ` Lee Revell
2004-07-28 21:15             ` Karim Yaghmour
2004-07-28 21:43               ` Lee Revell
2004-07-28 21:38                 ` Karim Yaghmour
2004-07-28 20:21         ` Bill Huey [this message]
2004-07-28 20:42           ` Lee Revell
2004-07-28 20:46             ` Bill Huey
2004-07-28 21:48           ` Karim Yaghmour
2004-07-28 22:30             ` Bill Huey
2004-07-28 22:03           ` Philippe Gerum
2004-07-29 20:33 Albert Cahalan

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=20040728202107.GA6952@nietzsche.lynx.com \
    --to=bhuey@lnxw.com \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manas.saksena@timesys.com \
    --cc=mingo@elte.hu \
    --cc=piggy@timesys.com \
    --cc=rlrevell@joe-job.com \
    --cc=rpm@xenomai.org \
    --cc=scott@timesys.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

all inboxes | Powered by JetHome®