From: Rick Jones <rick.jones2@hp.com>
To: michal.simek@petalogix.com
Cc: LKML <linux-kernel@vger.kernel.org>,
John Williams <john.williams@petalogix.com>,
netdev@vger.kernel.org, Grant Likely <grant.likely@secretlab.ca>,
John Linn <John.Linn@xilinx.com>,
"Steven J. Magnani" <steve@digidescorp.com>,
Arnd Bergmann <arnd@arndb.de>,
akpm@linux-foundation.org
Subject: Re: Network performance - iperf
Date: Mon, 29 Mar 2010 09:57:33 -0700 [thread overview]
Message-ID: <4BB0DBFD.30904@hp.com> (raw)
In-Reply-To: <4BB0D9A1.3090107@hp.com>
Rick Jones wrote:
> I don't know how to set fixed socket buffer sizes in iperf, if you were
> running netperf though I would suggest fixing the socket buffer sizes
> with the test-specific -s (affects local) and -S (affects remote) options:
>
> netperf -t TCP_STREAM -H <remote> -l 30 -- -s 32K -S 32K -m 32K
>
> to test the hypothesis that the autotuning of the socket buffers/window
> size is allowing the windows to grow in the larger memory cases beyond
> what the TLB in your processor is comfortable with.
BTW, by default, netperf will allocate a "ring" of send buffers - the number
allocated will be one more than the socket buffer size divided by the send size
- so in the example above, there will be two 32KB buffers allocated in netperf's
send ring. A similar calculation may happen on the receive side.
That can be controlled via the global (before the "--") -W option.
-W send,recv Set the number of send,recv buffers
So, you might make the netperf command:
netperf -t TCP_STREAM -H <remote> -l 30 -W 1,1 -- -s 32K -S 32K -m 32K
happy benchmarking,
rick jones
next prev parent reply other threads:[~2010-03-29 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 11:33 Network performance - iperf Michal Simek
2010-03-29 12:16 ` Eric Dumazet
2010-03-29 14:54 ` Michal Simek
2010-03-29 15:27 ` Michal Simek
2010-03-29 17:45 ` Eric Dumazet
2010-03-30 9:34 ` Michal Simek
2010-03-30 12:11 ` Steve Magnani
2010-03-30 12:41 ` Eric Dumazet
2010-03-29 16:47 ` Rick Jones
2010-03-29 16:57 ` Rick Jones [this message]
2010-03-29 20:07 ` 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=4BB0DBFD.30904@hp.com \
--to=rick.jones2@hp.com \
--cc=John.Linn@xilinx.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@petalogix.com \
--cc=netdev@vger.kernel.org \
--cc=steve@digidescorp.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.