From: Rick Jones <rick.jones2@hp.com>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: Netperf TCP_RR(loopback) 10% regression in 2.6.24-rc6, comparing with 2.6.22
Date: Fri, 11 Jan 2008 09:56:42 -0800 [thread overview]
Message-ID: <4787ADDA.7090602@hp.com> (raw)
In-Reply-To: <1200043854.3265.24.camel@ymzhang>
>>The test command is:
>>#sudo taskset -c 7 ./netserver
>>#sudo taskset -c 0 ./netperf -t TCP_RR -l 60 -H 127.0.0.1 -i 50,3 -I 99,5 -- -r 1,1
A couple of comments/questions on the command lines:
*) netperf/netserver support CPU affinity within themselves with the
global -T option to netperf. Is the result with taskset much different?
The equivalent to the above would be to run netperf with:
./netperf -T 0,7 ...
The one possibly salient difference between the two is that when done
within netperf, the initial process creation will take place wherever
the scheduler wants it.
*) The -i option to set the confidence iteration count will silently cap
the max at 30.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2008-01-11 17:56 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 [this message]
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
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=4787ADDA.7090602@hp.com \
--to=rick.jones2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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.