public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Huey (hui) <bhuey@lnxw.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "Bill Huey (hui)" <bhuey@lnxw.com>,
	Kristian Benoit <kbenoit@opersys.com>,
	linux-kernel@vger.kernel.org, andrea@suse.de, tglx@linutronix.de,
	karim@opersys.com, mingo@elte.hu, pmarques@grupopie.com,
	bruce@andrew.cmu.edu, nickpiggin@yahoo.com.au, ak@muc.de,
	sdietrich@mvista.com, dwalker@mvista.com, hch@infradead.org,
	akpm@osdl.org, rpm@xenomai.org
Subject: Re: PREEMPT_RT and I-PIPE: the numbers, take 3
Date: Thu, 30 Jun 2005 11:59:13 -0700	[thread overview]
Message-ID: <20050630185913.GA26707@nietzsche.lynx.com> (raw)
In-Reply-To: <42C408ED.5030306@tmr.com>

On Thu, Jun 30, 2005 at 10:59:57AM -0400, Bill Davidsen wrote:
> The reasons you have to repeat yourself are (a) you lack communications 
> skills and expect people to read past your insults, (b) you're just 
> technically wrong in some cases, such as saying that the results would 
> be different if the kernel were compiled in an unrealistic way.

I'm going to stick to my original points that I've already discussed in
a number of earlier threads. SMP is needed for this patch to really
work. What was not understood by folks, still isn't, is that the
functionality of this system is more extensive than a simple dual kernel
set up. This is not a personality or communication skills issue. It's
folks not understand the patch out of ignorance and irrational fear, how
it really works, and what advantages it gives over dual kernels.

A lot of it is just flat out ignorance about RTOS in the Linux community.
They confuse theoretical and practical issues and assume that they are
right when they don't write RT apps, don't understand the patch or the
direction it's going.

This material has been covered over and over again in previous threads,
but a disconnected, persistent and hysterical group still FUDs this patch
continuously, which is why I'm losing patience with this. If you're coming
in middle of this story it can certainly seem that way, but the reverse is
true. If I have to insult folks as a preventative for negative rumors about
this patch, then so be it.

> Your point that SMP operation is important is true, but I see no reason 
> to think Ingo has missed that.

No negative comments were directed at Ingo of any sort. The nature of RTOS
changes as hardware advances. That's all I'm saying.

bill


  reply	other threads:[~2005-06-30 18:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 22:29 PREEMPT_RT and I-PIPE: the numbers, take 3 Kristian Benoit
2005-06-29 22:57 ` Bill Huey
2005-06-29 23:03   ` Andrea Arcangeli
2005-06-29 23:33     ` Bill Huey
2005-06-29 23:54   ` Paul E. McKenney
2005-06-30  1:50     ` Bill Huey
2005-06-30  1:56       ` Nick Piggin
2005-06-30  2:14         ` Bill Huey
2005-06-30  2:09           ` Nick Piggin
2005-06-30  2:18             ` Bill Huey
2005-06-30  6:50               ` Steven Rostedt
2005-06-30 14:15               ` Zwane Mwaikambo
2005-06-30 19:08                 ` Bill Huey
2005-06-30  2:01       ` Nicolas Pitre
2005-06-30  2:16         ` Bill Huey
2005-06-30  2:19       ` Paul E. McKenney
2005-06-30 14:59       ` Bill Davidsen
2005-06-30 18:59         ` Bill Huey [this message]
2005-06-30  7:07     ` Ingo Molnar
2005-06-30 15:43       ` Paul E. McKenney
2005-06-30 16:17         ` Ingo Molnar
2005-06-30 16:48           ` Sven-Thorsten Dietrich
2005-06-30 23:08           ` Paul E. McKenney
2005-06-29 23:49 ` Paul E. McKenney
2005-06-30  5:55 ` Ingo Molnar
2005-06-30 10:32 ` Ingo Molnar
2005-06-30 16:55 ` Ingo Molnar

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=20050630185913.GA26707@nietzsche.lynx.com \
    --to=bhuey@lnxw.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=bruce@andrew.cmu.edu \
    --cc=davidsen@tmr.com \
    --cc=dwalker@mvista.com \
    --cc=hch@infradead.org \
    --cc=karim@opersys.com \
    --cc=kbenoit@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pmarques@grupopie.com \
    --cc=rpm@xenomai.org \
    --cc=sdietrich@mvista.com \
    --cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox