From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Bob \(Robert\) McMahon" <rmcmahon@broadcom.com>
Cc: "'make-wifi-fast@lists.bufferbloat.net'"
<make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] iperf enhancements in 2.0.8
Date: Wed, 21 Oct 2015 13:37:39 +0200 [thread overview]
Message-ID: <87oafsqwos.fsf@toke.dk> (raw)
In-Reply-To: <CCF12E84D46F914D86B3F9C1BC40E7991E5C8F2A@SJEXCHMB05.corp.ad.broadcom.com> (Bob McMahon's message of "Wed, 21 Oct 2015 00:06:08 +0000")
"Bob (Robert) McMahon" <rmcmahon@broadcom.com> writes:
> One can get the millisecond timestamps in the CSV two ways
>
> 1) use the -e option (for enhanced reporting)
> 2) use a value of less than 0.5 seconds for -i which enables
> enhanced reports without requiring -e (previous iperf verisons
> don't support faster than 0.5 sec so it's assumed a user setting
> it faster will also want enhanced reports)
Awesome, thanks! I'll add support for this to Flent. Is there a way to
detect whether or not iperf supports this extended timestamp format,
other than looking at the actual output? E.g. a command line switch that
will fail if the support is not there, something or grep for in a help
output or the like?
-Toke
next prev parent reply other threads:[~2015-10-21 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 4:19 Bob (Robert) McMahon
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 [this message]
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=87oafsqwos.fsf@toke.dk \
--to=toke@toke.dk \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rmcmahon@broadcom.com \
/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