public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Bill Huey (hui)" <bhuey@lnxw.com>
Cc: 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 10:59:57 -0400	[thread overview]
Message-ID: <42C408ED.5030306@tmr.com> (raw)
In-Reply-To: <20050630015041.GA24234@nietzsche.lynx.com>

Bill Huey (hui) wrote:
> On Wed, Jun 29, 2005 at 04:54:22PM -0700, Paul E. McKenney wrote:
> 
>>If you were suggesting this to be run on an SMP system, I would agree
>>with you.  I, too, would very much like to see these results run on a
>>2-CPU or 4-CPU system, although I am most certainly -not- asking Kristian
>>and Karim to do this work -- it is very much someone else's turn in the
>>barrel, I would say!
> 
> 
> No, I'm suggesting that you and other folks understand the basic ideas
> behind this patch and stop asking unbelievably stupid questions. This has
> been covered over and over again, and I shouldn't have to repeat these
> positions constantly because folks have both a language comprehension
> problem and inability to bug off appropriately.

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.
> 
> 
>>However, on a UP system, I have to agree with Kristian's choice of
>>configuration.  An embedded system developer running on a UP system would
>>naturally use a UP Linux kernel build, so it makes sense to benchmark
>>a UP kernel on a UP system.
> 
> 
> Dual cores are going to be standard in the next few years so RTOSs should
> anticipate these things coming down the pipeline.

s/standard/common/

I doubt that single core CPUs are going to vanish, there are too many 
power critical (heat critical) embedded applications. In many the 
response time is important but the total CPU capability isn't an issue 
while battery life or fanless operation is.

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

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2005-06-30 15:01 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 [this message]
2005-06-30 18:59         ` Bill Huey
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=42C408ED.5030306@tmr.com \
    --to=davidsen@tmr.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=bhuey@lnxw.com \
    --cc=bruce@andrew.cmu.edu \
    --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