> Indeed.  Setting tcp_delack_min to 0 completely eliminated the undesired 
quoted text
> latencies, though of course that would be a bit dangerous with naive 
> apps talking across the network. 

What did it do to the packets per second or per unit of work?  Depending 
on the nature of the race between the ACK returning from the remote and 
the application pushing more bytes into the socket, I'd think that 
setting the delayed ack timer to zero could result in more traffic on 
the network (those bare ACKs) than simply setting TCP_NODELAY at the source.

And since with small packets and/or copy avoidance an ACK is 
(handwaving) just as many CPU cycles at either end as a data segment 
that also means a bump in CPU utilization.

rick jones
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html