On Tue, 2018-02-06 at 15:22 +0000, David Laight wrote: > From: Eric Dumazet > > Sent: 06 February 2018 14:20 > > ... > > Please give exact details. > > Sending 64, 128, 256 or 512 bytes at a time on TCP_STREAM makes little > > sense. > > We are not optimizing stack for pathological cases, sorry. > > There are plenty of workloads which are not bulk data and where multiple > small buffers get sent at unknown intervals (which may be back to back). > Such connections have to have Nagle disabled because the Nagle delays > are 'horrid'. > Clearly lost packets can cause delays, but they are rare on local networks.
Auto corking makes sure aggregation happens, even for when Nagle is in the picture. netperf -- -m 256 will still cook 64KB TSO packets netperf is not adding delays between each send(), unless it has been modified.
