From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: LKML <linux-kernel@vger.kernel.org>, Netdev <netdev@vger.kernel.org>
Subject: Re: Netperf TCP_RR(loopback) 10% regression in 2.6.24-rc6, comparing with 2.6.22
Date: Mon, 14 Jan 2008 17:38:36 +0800 [thread overview]
Message-ID: <1200303516.3151.30.camel@ymzhang> (raw)
In-Reply-To: <Pine.LNX.4.64.0801141118450.31652@kivilampi-30.cs.helsinki.fi>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1064 bytes --]
On Mon, 2008-01-14 at 11:21 +0200, Ilpo Järvinen wrote:
> On Mon, 14 Jan 2008, Ilpo Järvinen wrote:
>
> > On Fri, 11 Jan 2008, Zhang, Yanmin wrote:
> >
> > > On Wed, 2008-01-09 at 17:35 +0800, Zhang, Yanmin wrote:
> > > >
> > > > As a matter of fact, 2.6.23 has about 6% regression and 2.6.24-rc's
> > > > regression is between 16%~11%.
> > > >
> > > > I tried to use bisect to locate the bad patch between 2.6.22 and 2.6.23-rc1,
> > > > but the bisected kernel wasn't stable and went crazy.
> >
> > TCP work between that is very much non-existing.
>
> I _really_ meant 2.6.22 - 2.6.23-rc1, not 2.6.24-rc1 in case you had a
> typo
I did bisect 2.6.22 - 2.6.23-rc1. I also tested it on the latest 2.6.24-rc.
> there which is not that uncommon while typing kernel versions... :-)
Thanks. I will retry bisect and bind the server/client to the same logical processor, where
I hope the result is stable this time when bisecting.
Manual testing showed there is still same or more regression if I bind the
processes on the same cpu.
Thanks a lot!
-yanmin
next prev parent reply other threads:[~2008-01-14 9:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 9:35 Netperf TCP_RR(loopback) 10% regression in 2.6.24-rc6, comparing with 2.6.22 Zhang, Yanmin
2008-01-09 11:48 ` David Miller
2008-01-11 9:30 ` Zhang, Yanmin
2008-01-11 17:56 ` Rick Jones
2008-01-14 3:11 ` Zhang, Yanmin
2008-01-14 17:46 ` Rick Jones
2008-01-22 5:24 ` Zhang, Yanmin
2008-01-22 6:07 ` Zhang, Yanmin
2008-01-22 6:22 ` David Miller
2008-01-22 6:51 ` Zhang, Yanmin
2008-01-22 7:13 ` Eric Dumazet
2008-01-22 6:27 ` Eric Dumazet
2008-01-22 6:52 ` Zhang, Yanmin
2008-01-22 7:32 ` David Miller
2008-01-22 18:36 ` Rick Jones
2008-01-23 0:42 ` Zhang, Yanmin
2008-01-23 3:25 ` Zhang, Yanmin
2008-01-14 8:44 ` Ilpo Järvinen
2008-01-14 9:21 ` Ilpo Järvinen
2008-01-14 9:38 ` Zhang, Yanmin [this message]
2008-01-14 10:53 ` Herbert Xu
2008-01-16 0:34 ` Zhang, Yanmin
2008-01-16 7:15 ` Zhang, Yanmin
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=1200303516.3151.30.camel@ymzhang \
--to=yanmin_zhang@linux.intel.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.