11 ms·
I believe SYN cookies affect the TCP window because the kernel can't actually guarantee it has enough RAM to allocate a reasonably sized buffer when it sends th
by makomk 11y ago
I believe SYN cookies affect the TCP window because the kernel can't actually guarantee it has enough RAM to allocate a reasonably sized buffer when it sends the SYN-ACK, as by design it doesn't allocate any memory until after the ACK is returned from the other side.
- felixge 11y agoSure, but after the connection is established, and "memory pressure" [1] is gone, shouldn't the tcp implementation grow the window again? [1] I'm putting this in quotes, because the machines in questions have ridiculous amounts of memory, and the pressure merely came from SOMAXCONN being at their default value of 128.
- cawoodfield 11y agoOne potential explanation depending on your kernel version - traditional SYN cookies cannot encode TCP extensions, including window scaling, which will (nearly) always result in slower transfers. Newer kernels (The Googles aren't giving me a kernel version, unfortunately) use the TCP timestamp option in addition to the sequence to encode a limited number of TCP options, including WS. More info: http://www.inesc-id.pt/pt/indicadores/Ficheiros/165.pdf http://www.inesc-id.pt/pt/indicadores/Ficheiros/165.pdf