From: Dave Taht <dave.taht@gmail.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>,
Rick Jones <rick.jones2@hp.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] RRUL for netperf (bad hack)
Date: Fri, 17 Apr 2015 11:20:22 -0700 [thread overview]
Message-ID: <CAA93jw7k6+eNPn5v_X0vmX3hnADdUUq_jdmjz2ARX_zrpHc-pw@mail.gmail.com> (raw)
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE9319BF1A5@xmb-aln-x05.cisco.com>
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)
<versteb@cisco.com> wrote:
> Lars-
>
> Looking now - Thinking back, I probably hacked it in myself. I do not see 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) <versteb@cisco.com> wrote:
>>
>> 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 stuff for UDP flows.
>
> Thanks,
> Lars
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
Open Networking needs **Open Source Hardware**
https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
next prev parent reply other threads:[~2015-04-17 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 14:45 Eggert, Lars
2015-04-17 16:18 ` Bill Ver Steeg (versteb)
2015-04-17 16:38 ` Eggert, Lars
2015-04-17 17:04 ` Bill Ver Steeg (versteb)
2015-04-17 18:20 ` Dave Taht [this message]
2015-04-18 12:33 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7k6+eNPn5v_X0vmX3hnADdUUq_jdmjz2ARX_zrpHc-pw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=rick.jones2@hp.com \
--cc=versteb@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox