From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g9t5008.houston.hp.com (g9t5008.houston.hp.com [15.240.92.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smtp.hp.com", Issuer "VeriSign Class 3 Secure Server CA - G3" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 46E5821F2FD for ; Wed, 22 Apr 2015 10:15:58 -0700 (PDT) Received: from g5t1633.atlanta.hp.com (g5t1633.atlanta.hp.com [16.201.144.132]) by g9t5008.houston.hp.com (Postfix) with ESMTP id 3FC2D247 for ; Wed, 22 Apr 2015 17:15:56 +0000 (UTC) Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51]) by g5t1633.atlanta.hp.com (Postfix) with ESMTP id B214D66 for ; Wed, 22 Apr 2015 17:15:56 +0000 (UTC) Message-ID: <5537D74C.7080100@hp.com> Date: Wed, 22 Apr 2015 10:15:56 -0700 From: Rick Jones User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: bloat@lists.bufferbloat.net References: <2C987A4B-7459-43C1-A49C-72F600776B00@gmail.com> <14cd9e74e48.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net> <20150422040453.GB36239@sesse.net> <1429676935.18561.42.camel@edumazet-glaptop2.roam.corp.google.com> <12383_1429692679_55376107_12383_9099_1_p7gmr0psut68sen0sao8o4lp.1429692550899@email.android.com> <1429710657.18561.68.camel@edumazet-glaptop2.roam.corp.google.com> <25065_1429716388_5537BDA4_25065_2328_1_63pyislbvtjf653k3qt8gw2c.1429715929544@email.android.com> <20150422155933.GA20218@sesse.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Bloat] RE : DSLReports Speed Test has latency measurement built-in 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, 22 Apr 2015 17:16:27 -0000 On 04/22/2015 09:19 AM, Dave Taht wrote: > > Has anyone added pacing to netperf yet? (I can do so, but would need > guidance as to what getopt option to add) ./configure --enable-intervals recompile netperf and then you can use: netperf ... -b -w If you want to be able to specify an interval shorter than the minimum time for the itimer you need to add --enable-spin to the ./configure - netperf will burn CPU time like there was no tomorrow, but you'll get the finer control on the burst interval. happy benchmarking, rick