- http://articles.techrepublic.com.com/5100-10878_11-1050878.html -- "TCP/IP options for high-performance data transmission"
- http://www.ussg.iu.edu/hypermail/linux/kernel/0102.0/0943.html -- LKML thread, "TCP_NOPUSH on FreeBSD, TCP_CORK on Linux"
- http://www.irbs.net/internet/postfix/0707/1097.html -- postfix thread, "dkim-milter signing terribly slow with Postfix, but not with sendmail"
- This becomes: "TCP_NODELAY, TCP_CORK, TCP_NOPUSH, etc (was: dkim-milter signing terribly slow...)"
LRO/TSO are safe to use on routers and bridges so long as all interfaces involved support the technique.
Large receive offload. Cannot guarantee refragmentation, and thus ought not generally be used on bridges or routers.
Generic receive offload. Generalizes LRO to guarantee possibility of refragmentation, but coalesces a proper subset of packets suitable for LRO.
TCP segmentation offload, also known as TCP Large Send.
Generic segmentation offload, introduced in Linux 2.6.18. Generalizes TSO to guarantee possibility of refragmentation.
TCP auto-tuning on Linux
- netdev 2009-03-11, "TCP rx window autotuning harmful at LAN context"
- The Pittsburgh Supercomputing Center's Linux TCP notes
TCP auto-tuning on FreeBSD
- Finally introduced in [FreeBSD 7.2] by Andre Oppermann:
With TCP send buffer auto scaling and the default values below it supports 20Mbit/s at 100ms and 10Mbit/s at 200ms. Both read and write buffer are auto-sized.
- Linux's TCP socket options
- FreeBSD's TCP socket options
- TCP and Linux' Pluggable Congestion Control Algorithms, a 2007 Linux Gazette article by René Pfeiffer
- 'net: Generic Receive Offload, Herbert Xu 2008-12-12 linux-net post
- GSO, The Linux Foundation
- Linux: TCP Segmentation Offload, KernelTrap 2002-09-03