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
| ||
|
Date: Wed, 21 Sep 2011 14:06:54 -0700 From: Ben Greear <greearb@...delatech.com> To: netdev <netdev@...r.kernel.org> Subject: MTU and TCP transmit offload. We saw something interesting while doing some testing on 3.0.4. We configured 2 Ethernet NICs with standard 1500 MTU, and added a mac-vlan on each, with MTU of 300. The goal was to generate as many ~300 byte TCP packets as possible, for load testing purposes. We configured our tool to open sockets on the mac-vlans and send/receive TCP (IPv4) traffic. This actually seems to work quite nicely, allowing user-space to do large writes (24k in our case), and it appears have lots of small packets on the wire. We still need to sniff with external system to verify this..but packets-per-second counters look good. Evidently this all works because macvlans know that the NIC can do TSO, and the '300' MTU is passed in the big packet given to the NIC. This got me thinking...at least for my purposes, it would be nice to have a per-socket 'MTU' setting. The idea is that you could ask the NIC to do the TSO at whatever 'mtu' you wanted, without having to resort to mac-vlans with artificially small MTU. So, is there any interest in supporting such a socket option? I can't think of any use besides TCP traffic load testing, but perhaps someone else can think of one? Or, is load-testing enough? Thanks, Ben -- Ben Greear <greearb@...delatech.com> Candela Technologies Inc http://www.candelatech.com -- 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
Powered by blists - more mailing lists