From: "Alex,Shi" <alex.shi@intel.com>
To: eric.dumazet@gmail.com, davem@davemloft.net
Cc: "Chen, Tim C" <tim.c.chen@intel.com>,
"Zhang, Yanmin" <yanmin.zhang@intel.com>,
linux-kernel@vger.kernel.org
Subject: TCP stream performance regression due to c377411f2494a931ff7facdbb3a6839b1266bcf6
Date: Fri, 18 Jun 2010 15:17:28 +0800 [thread overview]
Message-ID: <1276845448.2118.346.camel@debian> (raw)
In our netperf testing, TCP_STREAM56 shows about 20% or more performance
regression on WSM/NHM and tigerton machines. The testing boot up both
netserver and client on localhost. The testing command like this:
./snapshot_script_net TC_STREAM56 127.0.0.1
We found the following commit causes this issue.
c377411f2494a931ff7facdbb3a6839b1266bcf6
Revert this commit will recover this regression on all machine.
Regards!
Alex
next reply other threads:[~2010-06-18 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 7:17 Alex,Shi [this message]
2010-06-18 8:26 ` TCP stream performance regression due to c377411f2494a931ff7facdbb3a6839b1266bcf6 Zhang, Yanmin
2010-06-24 17:18 ` Eric Dumazet
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=1276845448.2118.346.camel@debian \
--to=alex.shi@intel.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@intel.com \
--cc=yanmin.zhang@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;
as well as URLs for NNTP newsgroup(s).