From: Rick Jones <rick.jones2@hp.com>
To: Ben Greear <greearb@candelatech.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: MTU and TCP transmit offload.
Date: Wed, 21 Sep 2011 16:58:22 -0700 [thread overview]
Message-ID: <4E7A7A1E.1070807@hp.com> (raw)
In-Reply-To: <4E7A765E.6020701@candelatech.com>
>>> Isn't that covered by setsockopt() support for TCP_MAX_SEG? With
>>> TSO what gets passed to the NIC isn't the MTU, but the
>>> connection's MSS derived (in part at least) from the MTU of the
>>> egress interface. If one had made a setsockopt(TCP_MAX_SEG) call
>>> prior to the connect() or listen() call, presumably that would
>>> have influenced the MSS exchange at connection establishment.
>>
>> Ohh, that looks promising!
>>
>> I'll give that a try.
>
> This works like a charm. I'm so glad I don't need to hack
> a new sockopt!
Glad it works for you.
happy benchmarking,
rick jones
One of these days I'll have to decide if I add that as an option to
netperf, which presently only does the getsockopt(TCP_MAX_SEG). Folks
with a strong preference one way or t'other should feel free to contact
me on the side or via netperf-talk at netperf.org.
prev parent reply other threads:[~2011-09-21 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 21:06 MTU and TCP transmit offload Ben Greear
2011-09-21 22:11 ` Rick Jones
2011-09-21 22:16 ` Ben Greear
2011-09-21 23:42 ` Ben Greear
2011-09-21 23:58 ` Rick Jones [this message]
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=4E7A7A1E.1070807@hp.com \
--to=rick.jones2@hp.com \
--cc=greearb@candelatech.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).