From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id EA4A021F773 for ; Wed, 21 Oct 2015 04:37:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1445427460; bh=ywRl8HXWcB1yYMDZky6JTAHDAEi622edafk8ePiXgcA=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=TQCMOaumtw69DZm/2sqM5i/rHuRAKEqfiEyJnLlcJGrUHzAm9puAOGCZ6a+n9WbFA QFhpsFXSNqsYml9pH31YuzgTVmn/D+cv3Os8gH0Hr0i32oPFoAoSA3aBbk3FOCm4fh +b78uXLaL1rv/fNwo7l7OQXM41Q8V3D2xuwGrDY8= Sender: toke@toke.dk Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id 72C9BC401AE; Wed, 21 Oct 2015 13:37:39 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: "Bob \(Robert\) McMahon" References: <87wpunyz33.fsf@toke.dk> Date: Wed, 21 Oct 2015 13:37:39 +0200 In-Reply-To: (Bob McMahon's message of "Wed, 21 Oct 2015 00:06:08 +0000") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87oafsqwos.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain 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 11:38:06 -0000 "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 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