[PATCH] Added NoDelay config option and nodelay subsystem option

[Tobias Ringstrom]

On Tue, 29 Jan 2002, Rick Jones wrote:

> OK, I can see now that it will stop where you had things stop, so
> clearly bwdelay+1 is insufficient, I think we need bwdelay+2 in this
> instance with a socket buffer size of bwdelay. I tried to diagram it out
> and it was ugly, but I think it result in at least two REQ's being set
> at once each time after the intial singleton and tripple.
> 
> The reason to have the socket buffer only bwdelay is so that when that
> first tripple hits the third response cannot go into the socket buffer
> and hit TCP until the fifth(?) request arrives, so the fourth response
> ACK's both the four request and the fifth request. (It does this because
> it was sent by the app to TCP after the fifth request arrived because
> the fifth request acked the second response) I think I have that right
> though I am in a maze of twist passages :)

...and do not want to go there either.  Yes, you might achieve what you
propose with a carefully selected socket buffer, but after a while you
will have to send a window update or some other little silly packet and
you're toast again...  You'll probably find a way around that too, but I'd
rather enable TCP_NODELAY and be done with it, I think.  :-)

/Tobias