From: "Bob (Robert) McMahon" <rmcmahon@broadcom.com>
To: "make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>
Subject: [Make-wifi-fast] iperf enhancements in 2.0.8
Date: Fri, 16 Oct 2015 04:19:56 +0000 [thread overview]
Message-ID: <CCF12E84D46F914D86B3F9C1BC40E7991E5BB067@SJEXCHMB05.corp.ad.broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2665 bytes --]
Hi,
Just an FYI for those who might be interested. We added RTT and CWND samples in iperf 2.0.8<https://sourceforge.net/projects/iperf2/> for the TCP transmitter (iperf client) as well as UDP mean/min/max/stdev in the iperf server (assumes the clocks are synched.) Also, much faster sampling is supported. These may be helpful to those trying to improve wi-fi performance. To get the output one needs to use the -e option. Also, RTT/CWND is linux only. Apple is evaluating the change set and *may* ship it with future phones and Mac OS X systems.
Full change set here:
* Fix portability, compile and tested with Linux, Win10, Win7, WinXP, MacOS and Android
* Require -u for UDP (-b no longer defaults to UDP)
* Improved performance
* Enhanced reporting with -e
* Support smaller report intervals (5 ms or greater)
* Support SO_RCVTIMEOUT for server reports regardless of no packets
* Server will close the socket after no received traffic per the -t value (default is 10 sec)
* Support SO_TIMESTAMP for kernel level packet timestamping
* Support end/end latency in mean/min/max/stdev format (UDP) (-e required)
* (assumes client and server clocks synched, e.g by Precision Time Protocol)
* Add local port to bind support (-B option) using colon as separator
* (e.g. iperf -c 192.168.100.100 -B 192.168.100.10:6001)
* Support TCP rate limited streams (via the -b) using token bucket
* Support packets per second (UDP) via pps as units, (e.g. -b 1000pps)
* Display PPS in both client and server reports (UDP) (-e required)
* Support realtime scheduler as a command line option (--realtime or -z, assumes proper user privileges)
* Improve client tx code path so actual tx offered rate will converge to the -b value
* Improve accuracy of microsecond delay calls (in platform independent manner)
* (Use of Kalman filter to predict delay errors and adjust delays per predicted error)
* Display target loop time in initial client header (UDP)
* Fix final latency report sent from server to client (UDP)
* Include standard deviation in latency output
* Suppress unrealistic latency output using (-/-/-/-)
* Support SO_SNDTIMEO on send so socket write won't block beyond -t (TCP)
* Use clock_gettime if available (preferred over gettimeofday())
* TCP write and error counts (TCP retries and CWND for linux) (-e required)
* TCP read count, TCP read histogram (8 bins) (-e required)
* TCP RTT and CWND values in client reports (-e required, Linux only, RTT units microseconds)
Bob McMahon
Broadcom Wi-Fi QA Engineer
[-- Attachment #2: Type: text/html, Size: 12778 bytes --]
next reply other threads:[~2015-10-16 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 4:19 Bob (Robert) McMahon [this message]
2015-10-16 8:52 ` Toke Høiland-Jørgensen
2015-10-16 16:03 ` Bob (Robert) McMahon
2015-10-21 0:06 ` Bob (Robert) McMahon
2015-10-21 11:37 ` Toke Høiland-Jørgensen
2015-10-21 22:19 ` Bob (Robert) McMahon
2015-10-26 16:15 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CCF12E84D46F914D86B3F9C1BC40E7991E5BB067@SJEXCHMB05.corp.ad.broadcom.com \
--to=rmcmahon@broadcom.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox