public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Bill Huey <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: Wed, 29 Jun 2005 16:54:22 -0700	[thread overview]
Message-ID: <20050629235422.GI1299@us.ibm.com> (raw)
In-Reply-To: <20050629225734.GA23793@nietzsche.lynx.com>

On Wed, Jun 29, 2005 at 03:57:34PM -0700, Bill Huey wrote:
> On Wed, Jun 29, 2005 at 06:29:24PM -0400, Kristian Benoit wrote:
> > Overall analysis:
> ...
> > We had not intended to redo a 3rd run so early, but we're happy we did
> > given the doubts expressed by some on the LKML. And as we suspected, these
> > new results very much corroborate what we had found earlier. As such, our
> > conclusions remain mostly unchanged:
> 
> Did you compile your host Linux kernel with CONFIG_SMP in place ? That's
> critical since a UP kernel removes both spinlock and blocking locks in
> critical paths makes micro benchmarks sort of invalid.
> 
> The benchmark is sort of confusing two things and merging them into one.
> Both the latency statistic and kernel performance must be kept seperate.
> The overall kernel performance is a more complicate issue that has to be
> analysize differently using a more complicated methodology. That because
> an RTOS use of PREEMPT_RT is going to be under a different circumstance
> than that of a pure dual kernel set up of some sort. The functionalities
> aren't the same.
> 
> I suggest that you compile the dual kernel with SMP turned on and try it
> again, otherwise it's not really testing the overhead of any of the locking
> for either the PREEMPT_RT or dual kernel set ups. That's really the only
> outstanding statistic that I've noticed in that benchmark.

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!

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.

						Thanx, Paul

  parent reply	other threads:[~2005-06-29 23:55 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 [this message]
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
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=20050629235422.GI1299@us.ibm.com \
    --to=paulmck@us.ibm.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