From: "Zhang, Yanmin" <yanmin.zhang@intel.com>
To: "Shi, Alex" <alex.shi@intel.com>,
"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: "Chen, Tim C" <tim.c.chen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: TCP stream performance regression due to c377411f2494a931ff7facdbb3a6839b1266bcf6
Date: Fri, 18 Jun 2010 16:26:23 +0800 [thread overview]
Message-ID: <33AB447FBD802F4E932063B962385B351F483A15@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <1276845448.2118.346.camel@debian>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 1261 bytes --]
More info about the testing:
It's a loopback testing. We start one client netperf process to communicate with netserver process in a stream TCP testing. To reduce the cpu cache effect, we bind the 2 processes on 2 different physical cpus.
#taskset -c 0 ./netserver
#taskset -c 15 ./netperf -t TCP_STREAM -l 60 -H 127.0.0.1 -i 50,3 -I 99,5 -- -s 57344 -S 57344 -m 4096
>>-----Original Message-----
>>From: Shi, Alex
>>Sent: 2010Äê6ÔÂ18ÈÕ 15:17
>>To: eric.dumazet@gmail.com; davem@davemloft.net
>>Cc: Chen, Tim C; Zhang, Yanmin; linux-kernel@vger.kernel.org
>>Subject: TCP stream performance regression due to
>>c377411f2494a931ff7facdbb3a6839b1266bcf6
>>
>>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
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
next prev parent reply other threads:[~2010-06-18 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 7:17 TCP stream performance regression due to c377411f2494a931ff7facdbb3a6839b1266bcf6 Alex,Shi
2010-06-18 8:26 ` Zhang, Yanmin [this message]
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=33AB447FBD802F4E932063B962385B351F483A15@shsmsx501.ccr.corp.intel.com \
--to=yanmin.zhang@intel.com \
--cc=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 \
/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).