AFAIK iperf is using the regular BSD socket API (discard this message if it does not). The BSP API provides very limited information but on the other hand it makes sure iperf numbers are exactly the numbers any application would get. Continued below.
2014-09-06 13:06 GMT+01:00 Martin T <m4rtn...@gmail.com>: > in case of blocking NIC drivers, how does the kernel signal the Iperf > client if buffers are full? Does those signals make the Iperf client > to do more or longer nanosleep() system calls between write() calls to > UDP socket in order to write less data to socket If the driver and the stack are "truly blocking", then iperf will simply block for longer in the write() call, which may reduce the throughput. Exactly like when writing to a (slow) TCP socket or a (busy) disk. > or does the signal sent by kernel include the amount of data dropped I don't think the BSP socket API can report anything like this. Cheers, Marc ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Iperf-users mailing list Iperf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iperf-users
