From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Eggert\, Lars" <lars@netapp.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] RRUL for netperf (bad hack)
Date: Sat, 18 Apr 2015 14:33:58 +0200 [thread overview]
Message-ID: <87y4lplio9.fsf@toke.dk> (raw)
In-Reply-To: <880D8FBB-3C10-451D-8EB5-50D0A65B9704@netapp.com> (Lars Eggert's message of "Fri, 17 Apr 2015 14:45:58 +0000")
"Eggert, Lars" <lars@netapp.com> writes:
> (I was interested in the delay an application sees on top of a TCP
> stream, which is not something Toke's excellent netperf-wrapper tool
> can currently do, AFAIK.)
You're quite right. If a version of this makes it upstream in netperf,
I'm quite happy to add in a parser for it so it can be used with the
other tests in netperf-wrapper :)
-Toke
prev parent reply other threads:[~2015-04-18 12:34 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
2015-04-18 12:33 ` Toke Høiland-Jørgensen [this message]
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=87y4lplio9.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=lars@netapp.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