Re: TSO on veth device slows transmission to a crawl

[Rick Jones <rick.jones2@hp.com>]

On 04/08/2015 10:09 AM, Jan Engelhardt wrote:
> The problem won't manifest with netperf even if run for extended
> period (60 seconds). netperf is probably too smart, exploiting some
> form of parallelism.

Heh - I rather doubt netperf is all that smart.  Unless you use the 
likes of the -T global option to bind netperf/netserver to specific 
CPUs, it will just blythly run wherever the stack/scheduler decides it 
should run.

It is though still interesting you don't see the issue with netperf.  I 
don't know specifically how xinetd-chargen behaves but if it is like the 
chargen of old, I assume that means it is sitting there writing one byte 
at a time to the socket, and perhaps has TCP_NODELAY set.  If you want 
to emulate that with netperf, then something like:

netperf -H <receiver> -t TCP_STREAM -- -m 1 -D

would be the command-line to use.

happy benchmarking,

rick jones