From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 20D4F21F570 for ; Fri, 17 Apr 2015 11:20:23 -0700 (PDT) Received: by oift201 with SMTP id t201so83545859oif.3 for ; Fri, 17 Apr 2015 11:20:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=cJOuXRKJbwpwRMWRcmekvzCe6IuFx7W1jfYrSUWP1AE=; b=axdcWv9Uj1f7MJeYhSLBenIuAMF+WQXC/3vmeMOfEBMUz16CMFLV9UaG9mSP8OfhCM gRoD9Zvc6ZnI+pVG1//olHG8wyMeMqn+YDq12uCjN2z5FYt5gmNj5AU4ztC98+EhqMxF dOdkYpUQib1hyaE8ONplgJdux/vWGAH+4IxfIAi/hTGp+ASM4FCZq0KUrgAU0kHNKFkP 1KWMHExDNg0UMFlPHa4u7dBE1Zl788E89dMbklsfTxX9AjvePgssPx46rFazqYslOLEW yrMqwpuq4e3NK4vrXq3XZZ5skkVEIyz9sa4GPjMQpxGJ4KPaY25d9d9i4NYTfbNPXsv7 2fsQ== MIME-Version: 1.0 X-Received: by 10.60.98.2 with SMTP id ee2mr4156307oeb.39.1429294822917; Fri, 17 Apr 2015 11:20:22 -0700 (PDT) Received: by 10.202.71.139 with HTTP; Fri, 17 Apr 2015 11:20:22 -0700 (PDT) In-Reply-To: References: <880D8FBB-3C10-451D-8EB5-50D0A65B9704@netapp.com> Date: Fri, 17 Apr 2015 11:20:22 -0700 Message-ID: From: Dave Taht To: "Bill Ver Steeg (versteb)" , Rick Jones Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: bloat Subject: Re: [Bloat] RRUL for netperf (bad hack) 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: Fri, 17 Apr 2015 18:20:52 -0000 I am delighted to see this functionality in netperf, however hacky. We could use to also do something tcp-like in udp, with timestamping like this (perhaps using the SO_TIMESTAMPING api in linux for increased accuracy on rx)... Getting better tools, one patch at a time, one tool at a time, one daemon at a time... On Fri, Apr 17, 2015 at 10:04 AM, Bill Ver Steeg (versteb) wrote: > Lars- > > Looking now - Thinking back, I probably hacked it in myself. I do not se= e it on my road Linux laptop, so I will check on my servers when I am back = in the office. > > > > Bill Ver Steeg > > > > -----Original Message----- > From: Eggert, Lars [mailto:lars@netapp.com] > Sent: Friday, April 17, 2015 12:38 PM > To: Bill Ver Steeg (versteb) > Cc: bloat > Subject: Re: RRUL for netperf (bad hack) > > Hi, > > On 2015-4-17, at 18:18, Bill Ver Steeg (versteb) wrot= e: >> >> Iperf also has some one-way and two-way delay measurements (or at least = the version I used last year did). It also put timestamps in the payload of= the packets. > > got a pointer to that version of iperf? I only see some latency-related s= tuff for UDP flows. > > Thanks, > Lars > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat --=20 Dave T=C3=A4ht Open Networking needs **Open Source Hardware** https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67