[netperf-talk] PAD_TIME in 2.4.5

[Rick Jones]

>> Also, if there is indeed that much buffering in the modem(s) you
>> might want to consider explicit, smaller socket buffer sizes than
>> system defaults.  I wouldn't be surprised if Linux autotuning
>> didn't play all that well here either, which would be another
>> reason to go with explicitly set socket buffer sizes.
>>
> Is this the -- -s command line option?

That and the -S one.  For example:

netperf -H remote -- -s 32K -S 60k

will set the local (netperf side -s) socket buffer sizes to 32768 bytes, 
and will set the remote (netserver side, via -S) socket buffer sizes to 
60000 bytes.

http://www.netperf.org/svn/netperf2/trunk/doc/netperf.html#index-g_t_002ds_002c-Test_002dspecific-63

rick jones