netdev - Re: MTU and TCP transmit offload.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4E7A7A1E.1070807@hp.com>
Date:	Wed, 21 Sep 2011 16:58:22 -0700
From:	Rick Jones <rick.jones2@...com>
To:	Ben Greear <greearb@...delatech.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: MTU and TCP transmit offload.

>>> 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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html