From: Karim Yaghmour <karim@opersys.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Kristian Benoit <kbenoit@opersys.com>,
linux-kernel@vger.kernel.org, paulmck@us.ibm.com, bhuey@lnxw.com,
andrea@suse.de, tglx@linutronix.de, 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, part 4
Date: Sat, 09 Jul 2005 11:39:53 -0400 [thread overview]
Message-ID: <42CFEFC9.7070007@opersys.com> (raw)
In-Reply-To: <20050709071911.GB31100@elte.hu>
Ingo Molnar wrote:
> yeah, they definitely have helped, and thanks for this round of testing
> too! I'll explain the recent changes to PREEMPT_RT that resulted in
> these speedups in another mail.
Great, I'm very much looking forward to it.
> Looking at your numbers i realized that the area where PREEMPT_RT is
> still somewhat behind (the flood ping +~10% overhead), you might be
> using an invalid test methodology:
I've got to smile reading this :) If one thing became clear out of
these threads is that no matter how careful we are with our testing,
there is always something that can be criticized about them.
Take the highmem thing, for example, I never really bought the
argument that highmem was the root of all evil ;) , and the last
comparison we did between 50-35 and 51-02 with and without highmem
clearly showed that indeed while highmem is a factor, there are
inherent problems elsewhere than the disabling of highmem doesn't
erase. Also, both vanilla and I-pipe were run with highmem, and if
they don't suffer from it, then the problem is/was with PREEMPT_RT.
With ping floods, as with other things, there is room for
improvement, but keep in mind that these are standard tests used
as-is by others to make measurements, that each run is made 5
times, and that the values in those tables represent the average
of 5 runs. So while they may not be as exact as could be, I don't
see why they couldn't be interpreted as giving us a "good idea" of
what's happening.
For one thing, the heavy fluctuation in ping packets may actually
induce a state in the monitored kernel which is more akin to the
one we want to measure than if we had a steady flow of packets.
I would usually like very much to entertain this further, but we've
really busted all the time slots I had allocated to this work. So at
this time, we really think others should start publishing results.
After all, our results are no more authoritative than those
published by others.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2005-07-09 15:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 23:01 PREEMPT_RT and I-PIPE: the numbers, part 4 Kristian Benoit
2005-07-09 1:28 ` Karim Yaghmour
2005-07-09 7:19 ` Ingo Molnar
2005-07-09 15:39 ` Karim Yaghmour [this message]
2005-07-09 15:53 ` Karim Yaghmour
2005-07-09 15:53 ` Karim Yaghmour
2005-07-11 7:05 ` Ingo Molnar
2005-07-11 11:25 ` Karim Yaghmour
2005-07-09 17:22 ` Daniel Walker
2005-07-09 23:37 ` Bill Huey
2005-07-09 9:01 ` Paul Rolland
2005-07-09 14:47 ` Karim Yaghmour
2005-07-09 15:22 ` Ingo Molnar
2005-07-11 5:24 ` 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=42CFEFC9.7070007@opersys.com \
--to=karim@opersys.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=kbenoit@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=paulmck@us.ibm.com \
--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