[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <33AB447FBD802F4E932063B962385B351F483A15@shsmsx501.ccr.corp.intel.com>
Date: Fri, 18 Jun 2010 16:26:23 +0800
From: "Zhang, Yanmin" <yanmin.zhang@...el.com>
To: "Shi, Alex" <alex.shi@...el.com>,
"eric.dumazet@...il.com" <eric.dumazet@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>
CC: "Chen, Tim C" <tim.c.chen@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: TCP stream performance regression due to
c377411f2494a931ff7facdbb3a6839b1266bcf6
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@...il.com; davem@...emloft.net
>>Cc: Chen, Tim C; Zhang, Yanmin; linux-kernel@...r.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
Powered by blists - more mailing lists