Hi Freeman,
Iperf UDP just opens a socket and doesn't self regulate per se. Dropping
packet on TX if the offered rate exceeds the link rate is expected.
What I've seen in the past is related to the network driver. If the driver
blocks on a socket write than you will see "self regulation" on TX.
What network device are you using?
Bob
From: Freeman (Xiaoguang) Wang [mailto:freem...@broadcom.com]
Sent: Monday, July 07, 2014 8:00 PM
To: iperf-users@lists.sourceforge.net
Subject: [Iperf-users] Different iperf UDB behaviour on Fedora 14 and 18
Hi
We were test iperf UDP and found with old releases like Fedora 14, iperf TX
side does not know the limitation of the link and keeps send at a data rage
specified by the command line, so at the TX side we observe lots of packet
drops. However, with Fedora 18 and above, it seems iperf UDP traffic is
self-regulated and automatically find out the best data rate, and the RX side
hardly shows any packet drop.
Anybody know the reason? It looks we actually ran the same version of iperf
2.0.5 on both systems.
Thanks
FRW
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users
