From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-23-ewr.dyndns.com (mxout-128-ewr.mailhop.org [216.146.33.128]) by lists.bufferbloat.net (Postfix) with ESMTP id 1DACE2E09C8 for ; Wed, 23 Mar 2011 12:27:46 -0700 (PDT) Received: from scan-21-ewr.mailhop.org (scan-21-ewr.local [10.0.141.243]) by mail-23-ewr.dyndns.com (Postfix) with ESMTP id 4E1EA43524 for ; Wed, 23 Mar 2011 19:27:46 +0000 (UTC) X-Spam-Score: 0.0 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 200.9.255.130 Received: from guug.org (guug.galileo.edu [200.9.255.130]) by mail-23-ewr.dyndns.com (Postfix) with ESMTP id BC90042F42; Wed, 23 Mar 2011 19:27:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) (uid 1001) by guug.org with local; Wed, 23 Mar 2011 13:27:40 -0600 id 020000A8.4D8A49AC.00002DF8 Date: Wed, 23 Mar 2011 13:27:40 -0600 From: Otto Solares To: Jonathan Morton Message-ID: <20110323192740.GI30600@guug.org> References: <0D59AD34-AA64-4376-BB8E-58C5D378F488@gmail.com> <4D829B58.1070601@swin.edu.au> <20110323103357.GG30600@guug.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: bloat , bloat-devel Subject: Re: [Bloat] Progress with latency-under-load tool X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2011 19:27:47 -0000 On Wed, Mar 23, 2011 at 01:26:59PM +0200, Jonathan Morton wrote: > Unfortunately that patch will not work - it completely breaks part of the on-wire protocol. It is much better to simply convert the final results for an auxiliary display. Yeah, after hours of running some results seems wrong, hopefully is not broken on my missing part of converting a float to network byte order. > I should also point out that I have very strong reasons for providing the measurements in non-traditional units by default. I'm measuring characteristics as they matter to applications and users, who measure things in bytes and frames per second, not bits and milliseconds. It is also much easier to get nontechnical people (who tend to be in charge of budgets) to respond to bigger-is-better numbers. Understood your PoV, sadly even my bosses (who lacks any degree of technicallity) knows that the Internet is sold to us in Mb/s (decimal) and delay (as he call it) is measured in ms. Good luck doing that nontechnical people use a CLI tool! ;) - Otto