From: Mike Galbraith <efault@gmx.de>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
alex.shi@intel.com, linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: UDP-U stream performance regression on 32-rc1 kernel
Date: Thu, 05 Nov 2009 09:57:18 +0100 [thread overview]
Message-ID: <1257411438.6497.13.camel@marge.simson.net> (raw)
In-Reply-To: <1257404598.6406.11.camel@marge.simson.net>
On Thu, 2009-11-05 at 08:03 +0100, Mike Galbraith wrote:
> On Thu, 2009-11-05 at 06:20 +0100, Mike Galbraith wrote:
> > On Thu, 2009-11-05 at 10:20 +0800, Zhang, Yanmin wrote:
> > > On Wed, 2009-11-04 at 13:07 +0100, Mike Galbraith wrote:
> >
> > > > Can you try the below, and send me
> > > I tested it on Nehalem machine against the latest tips kernel. netperf loopback
> > > result is good and regression disappears.
> >
> > Excellent. Ingo has picked up a version in tip (1b9508f) which has zero
> > negative effect on my x264 testcase, and is a win for mysql+oltp through
> > the whole test spectrum. As that may (dunno, Ingo?) now be considered a
> > regression fix, ie candidate for 32.final, testing that it does no harm
> > to your big machines would be a good thing. (pretty please?:)
>
> Egad. Size XXL difference on my cheap Q6600 box
Ingo, ignore my "eek!" reaction (for now).
I'm trying to test the pull lineup with as many benchmarks as I can fit
in, but methinks I'm screwing this one (unfamiliar) up :-/
> git v2.6.32-rc6-26-g91d3f9b
> Socket Message Elapsed Messages
> Size Size Time Okay Errors Throughput
> bytes bytes secs # # 10^6bits/sec
>
> 65536 4096 60.00 7793073 0 4256.06
> 65536 60.00 7780487 4249.18
>
> git v2.6.32-rc6-26-g91d3f9b + 1b9508f
> Socket Message Elapsed Messages
> Size Size Time Okay Errors Throughput
> bytes bytes secs # # 10^6bits/sec
>
> 65536 4096 60.00 15133547 0 8264.93
> 65536 60.00 15131466 8263.80
>
> tip v2.6.32-rc6-1796-gd995f1d
> Socket Message Elapsed Messages
> Size Size Time Okay Errors Throughput
> bytes bytes secs # # 10^6bits/sec
>
> 65536 4096 60.00 13998562 0 7645.08
> 65536 60.00 13986112 7638.28 (uhoh, tinker time.)
>
> -Mike
next prev parent reply other threads:[~2009-11-05 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 3:47 UDP-U stream performance regression on 32-rc1 kernel Alex Shi
2009-11-03 4:33 ` Zhang, Yanmin
2009-11-03 9:09 ` Mike Galbraith
2009-11-03 17:45 ` Ingo Molnar
2009-11-04 1:55 ` Zhang, Yanmin
2009-11-04 12:07 ` Mike Galbraith
2009-11-05 2:20 ` Zhang, Yanmin
2009-11-05 5:20 ` Mike Galbraith
2009-11-05 7:03 ` Mike Galbraith
2009-11-05 8:57 ` Mike Galbraith [this message]
2009-11-05 7:44 ` Zhang, Yanmin
2009-11-05 8:10 ` Mike Galbraith
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=1257411438.6497.13.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=alex.shi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yanmin_zhang@linux.intel.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