From: Rick Jones <rick.jones2@hp.com>
To: Michael Iatrou <m.iatrou@freemail.gr>
Cc: netdev@oss.sgi.com
Subject: Re: e1000 (?) jumbo frames performance issue
Date: Thu, 05 May 2005 13:17:31 -0700 [thread overview]
Message-ID: <427A7F5B.8050704@hp.com> (raw)
In-Reply-To: <200505051928.32496.m.iatrou@freemail.gr>
Michael Iatrou wrote:
> Hi,
> I did several benchmarks using Intel e1000 NIC and it seems there is a
> network throughput problem for MTU > 12000 (e1000 supports up to 16110
> MTU).
>
> Configuration:
> Two identical PCs, connected back to back, Intel Xeon 2.8GHz (SMP/SMT
> disabled), 512MB RAM, e1000 (82546EB)
>
> Linux 2.6.11.7
> netperf 2.3pl1
What settings, if any, did you use for -s, -S and in particular -m in netperf?
I seem to recall that some of the stack defaults for SO_SNDBUF (IIRC) would
result in netperf sending 16KB at a time into the connection - once you sent the
MTU above 16K you may have started running into issues with Nagle and delayed
ACK? You could try some tests adding a test-specific -D to disable Nagle, or -C
to set TCP_CORK, or use -m to set the send size to say, 32KB.
It might be good to add CPU utilization figures - for 2.3pl1 that means editing
the makefile to add a -DUSE_PROC_STAT and recompiling. Or you can grab netperf
2.4.0-rc3 from:
ftp://ftp.cup.hp.com/dist/networking/benchmarks/netperf/experimental/
if you cannot find it elsewhere, and that will (try to) compile-in the right CPU
utilization mechanism automagically.
rick jones
next prev parent reply other threads:[~2005-05-05 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 16:28 e1000 (?) jumbo frames performance issue Michael Iatrou
2005-05-05 20:17 ` Rick Jones [this message]
2005-05-05 21:33 ` David S. Miller
2005-05-05 21:54 ` Rick Jones
2005-05-05 22:17 ` David S. Miller
2005-05-05 23:24 ` Rick Jones
2005-05-05 21:55 ` Michael Iatrou
2005-05-05 22:26 ` Michael Iatrou
2005-05-06 16:18 ` Rick Jones
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=427A7F5B.8050704@hp.com \
--to=rick.jones2@hp.com \
--cc=m.iatrou@freemail.gr \
--cc=netdev@oss.sgi.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).