From: Rick Jones <rick.jones2@hp.com>
To: Linux Network Development list <netdev@vger.kernel.org>
Subject: a wrinkle to consider when benchmarking with LRO
Date: Wed, 09 May 2007 15:22:46 -0700 [thread overview]
Message-ID: <464249B6.6050506@hp.com> (raw)
At the risk of pointing-out the known/obvious...
I have been evaluating a system and its ability to source data across a 10G
link. My number of 10G sink's is a triffle minimal. To maximize the sinks'
ability to sink data I enabled large receive offload. The kernel on the sinks
was 2.6.21.1. The kernel on the source was "another OS."
While TSO doesn't especially change what is seen on the wire, LRO can. When the
NIC/driver combines the segments, the receiving TCP sends fewer ACKs. In short,
LRO is an implicit/backdoor ACK avoidance heuristic.
So, the sending TCP will receive fewer ACKs and will have a correspondingly
lower CPU overhead and so will be able to source data faster than if it were
sending to a system without LRO enabled.
I'm not trying to say this is a bad thing - in fact, I have gone on record a
number of times supporting good ACK avoidance heuristics - I just wanted to make
sure this behaviour I was seeing was on the record somewhere as it may not be
obvious to everyone.
happy benchmarking,
rick jones
reply other threads:[~2007-05-09 22:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=464249B6.6050506@hp.com \
--to=rick.jones2@hp.com \
--cc=netdev@vger.kernel.org \
/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).