Handle the case that Tcp socket is not ready for write

GoogleCodeExporter commented 9 years ago

imported from: http://argus-bg.dnsalias.org/issues/579

   1. Default: send blocking and force wait till send complete
   2. Option: Skip that send and jump to next send (consider, whether to inc sequence number or not)
   3. In both modes, add counter for number of times TCP was not ready for write (MSG_DONTWAIT that resulted in EWOULDBLOCK) and show that counter in summary statistics (together with dropped packets and so on). In case this error occurred, the statistics should tell the user about the other option to use the other mode

Original issue reported on code.google.com by igor.ivanov@itseez.com on 4 Apr 2011 at 7:42

GoogleCodeExporter commented 9 years ago

Original comment by igor.ivanov@itseez.com on 22 Apr 2011 at 3:14

Changed state: Started

GoogleCodeExporter commented 9 years ago

It looks close with #7

Original comment by igor.ivanov@itseez.com on 29 Apr 2011 at 7:05

GoogleCodeExporter commented 9 years ago

r54
This ability is enclosed in EXTRA_ABILITY macro definition. It is disabled in 
build process by default. User needs to set --enable-extra option in configure 
as ($ ./configure --prefix=<path to install> --enable-extra) to make 
functionality workable.

Original comment by igor.ivanov@itseez.com on 13 May 2011 at 6:37

Changed state: Fixed

DD1984 / sockperf

Handle the case that Tcp socket is not ready for write #25