From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: dpreed@reed.com, Dave Taht <dave@taht.net>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] 1Gbit/20Mbit D/L with ack-filtering
Date: Wed, 29 Nov 2017 23:43:47 +0100 [thread overview]
Message-ID: <87po80ogd8.fsf@toke.dk> (raw)
In-Reply-To: <1511994846.127314610@apps.rackspace.com>
dpreed@reed.com writes:
> BTW, one annoying thing about flent is that netperf is not available
> in fedora, rhel, centos as a package. So I have to install it and it
> doesn't just plug in smoothly. That's just my convenience issue. I
> don't use netperf myself on any of my systems. iperf and iperf3 seem
> to be a lot more pervasive these days...
Yeah, I think this is because of the weird license of netperf. However,
netperf has quite a few features that the iperf versions are lacking, so
it's not quite trivial to switch between them...
-Toke
prev parent reply other threads:[~2017-11-29 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 20:57 Dave Taht
2017-11-29 22:34 ` dpreed
2017-11-29 22:43 ` 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po80ogd8.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=dpreed@reed.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