News for hackers. Stuff that matters.
Re:It's always TCP_NODELAY by somat on Thursday May 09, 2024 @04:21PM (#40312569)
What about the opposite, disable delayed acks.

The problem is the pathological behavior when tinygram prevention interacts with delayed acks. There is an exposed option to turn off tinygram prevention(TCP_NODELAY), how would you tun off delayed acks instead? Say if you wanted to benchmark all four combinations and see what works best.

doing a little research I found:

linux has the TCP_QUICKACK socket option but you have to set it every time you receive. there is also /proc/sys/net/ipv4/tcp_delack_min and /proc/sys/net/ipv4/tcp_ato_min

freebsd has net.inet.tcp.delayed_ack and net.inet.tcp.delacktime

Re:It's always TCP_NODELAY by mjb on Thursday May 09, 2024 @05:13PM (#40313027)
TCP_QUICKACK does fix the worst version of the problem, but doesn't fix the entire problem. Nagles algorithm will still wait for up to one round-trip time before sending data (at least as specified in the RFC), which is extra latency with nearly no added value.
Re:It's always TCP_NODELAY by Animats on Thursday May 09, 2024 @04:36PM (#40312712)
> linux has the TCP_QUICKACK socket option but you have to set it every time you receive

Right. What were they thinking? Why would you want it off only some of the time?

Re:It's always TCP_NODELAY by batmanthehorse on Thursday May 09, 2024 @04:51PM (#40312844)
In CentOS/RedHat you can add `quickack 1` to the end of a route to tell it to disable delayed acks for that route.
Re:It's always TCP_NODELAY by rbjorklin on Thursday May 09, 2024 @09:23PM (#40314667)
And with systemd >= 253 you can set it as part of the network config to have it be applied automatically. https://github.com/systemd/systemd/issues/25906
Re:It's always TCP_NODELAY by Culonavirus on Friday May 10, 2024 @03:14AM (#40316176)
Apparently you have time to "do a little research" but not to read the entire article you're reacting to? It specifically mentions TCP_QUICKACK.