Kacheong Poon writes: > Roch - PAE wrote: > > > If the hearth of the matter is doing something Nagle-like > > for loopback connection, how about introducing a minimum > > time delay between wakeups of the reader (if TCP_NODELAY is > > not set of course). > > > > With Nagle, there is a natural delay which is proportional > > to the RTT. But fused connection, we could just have > > N times (say 20->50 times) bigger than the scheduling > > overhead. > > > It is worth trying. But I suspect that the delay may > need to be dynamic and adaptive. For example, if the app is > doing a simple request/response type of transaction, the > above will introduce the minimum delay for every request and > response. >
Apps that uses multiple small writes for a requests then wait for a response benefit greatly from setting TCP_NODELAY as this would bypass the block in both networked and fused case. -r _______________________________________________ networking-discuss mailing list [email protected]
