Re: [tcpm] Nagle Algorithm and Delayed ACKs

[Carsten Bormann <[e-mail]>]

On Jul 24, 2009, at 21:52, Thomas Narten wrote:

> TCP_NODELAY

My view would be that this is a well-documented option in the socket  
interface.
Even though the interaction with delayed ACKs is rarely explained  
correctly, there are lots of "Socket FAQ" and "Tuning Guide" documents  
that explain "Nagling" (ouch) and the TCP_NODELAY socket option (I get  
117000 google hits...).
TCP_NODELAY certainly is standard fare in any reasonable socket API  
course.
People already need to think about the number of write/send operations  
they perform for one message.
(Note that Linux also has TCP_CORK.)

In essence, the kernel needs to know whether the programmer was not  
considering the issue (making it likely there will be lots of silly  
small writes) or whether the issue was considered and the program is  
optimized with respect to the writes.
A socket option defaulting to the first case sounds like the right way  
to communicate that information, which is hard to infer.

What would you want to improve?

Gruesse, Carsten