From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gw1-out.broadcom.com (mail-gw1-out.broadcom.com [216.31.210.62]) by huchra.bufferbloat.net (Postfix) with ESMTP id 3122521F6FD for ; Wed, 21 Oct 2015 15:19:46 -0700 (PDT) X-IronPort-AV: E=Sophos;i="5.20,179,1444719600"; d="scan'208";a="78429094" Received: from irvexchcas08.broadcom.com (HELO IRVEXCHCAS08.corp.ad.broadcom.com) ([10.9.208.57]) by mail-gw1-out.broadcom.com with ESMTP; 21 Oct 2015 17:16:16 -0700 Received: from SJEXCHCAS05.corp.ad.broadcom.com (10.16.203.12) by IRVEXCHCAS08.corp.ad.broadcom.com (10.9.208.57) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 21 Oct 2015 15:19:44 -0700 Received: from SJEXCHMB05.corp.ad.broadcom.com ([fe80::4ccf:d24d:fe6c:9594]) by SJEXCHCAS05.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0235.001; Wed, 21 Oct 2015 15:19:44 -0700 From: "Bob (Robert) McMahon" To: "toke@toke.dk" Thread-Topic: [Make-wifi-fast] iperf enhancements in 2.0.8 Thread-Index: AQHRC/TjYWYd/fitd0eYN+GkXWJZTp52g+4w Date: Wed, 21 Oct 2015 22:19:43 +0000 Message-ID: References: <87wpunyz33.fsf@toke.dk> <87oafsqwos.fsf@toke.dk> In-Reply-To: <87oafsqwos.fsf@toke.dk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.16.203.100] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "'make-wifi-fast@lists.bufferbloat.net'" Subject: Re: [Make-wifi-fast] iperf enhancements in 2.0.8 X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2015 22:20:09 -0000 Hi Toke, I just committed -e, --enhancedreports information to the -h help text. = One can grep that output to see if the functionality is supported or not. = You'll need to pick up the latest from sourceforge. [rmcmahon@rjm-sfast-utf:~/UTF/svn/unittest] $ /projects/hnd_sig_ext16/rmcma= hon/Code/iperf/sourceforge/iperf2-code/src/iperf -h Usage: iperf [-s|-c host] [options] iperf [-h|--help] [-v|--version] Client/Server: -b, --bandwidth #[KMG | pps] bandwidth to send at in bits/sec or packets= per second -e, --enhancedreports use enhanced reporting giving more tcp/udp and t= raffic information -f, --format [kmKM] format to report: Kbits, Mbits, KBytes, MBytes ... Bob -----Original Message----- From: toke@toke.dk [mailto:toke@toke.dk]=20 Sent: Wednesday, October 21, 2015 4:38 AM To: Bob (Robert) McMahon Cc: 'make-wifi-fast@lists.bufferbloat.net' Subject: Re: [Make-wifi-fast] iperf enhancements in 2.0.8 "Bob (Robert) McMahon" 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 dete= ct 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 li= ke? -Toke