From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jonathan Foulkes <jf@jonathanfoulkes.com>,
Rich Brown <richb.hanover@gmail.com>,
rpm@lists.bufferbloat.net
Subject: Re: [Rpm] Alternate definitions of "working condition" - unnecessary?
Date: Thu, 07 Oct 2021 18:40:40 +0200 [thread overview]
Message-ID: <87bl40n5yv.fsf@toke.dk> (raw)
In-Reply-To: <7B6803AB-A910-4BD0-A4E8-63E7CD600790@jonathanfoulkes.com>
Jonathan Foulkes via Rpm <rpm@lists.bufferbloat.net> writes:
> Let me add another tool, as it’s the one I use to ensure I measure
> full line capacity during our tuning tests. Netperf.
[...]
> But for research, I total agree Flent is great tool. Just wish it was
> easier to tweak parameters, maybe I just need to use it more ;-)
Fun fact: I originally started working on Flent because I grew tired of
manually running 'netperf' tests. The original name was literally
'netperf-wrapper' ;)
The original idea was that you'd customise it by writing new test
definition files. Of course it has since turned out to be useful to
customise things more at runtime, and Flent has grown quite a few
features in that direction since. But the original legacy endures, so
there are certainly things you can only do by writing test definition
files.
Anyway, specific feature requests are always welcome! :)
-Toke
next prev parent reply other threads:[~2021-10-07 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 19:11 Rich Brown
2021-10-06 20:36 ` Jonathan Foulkes
2021-10-07 16:40 ` Toke Høiland-Jørgensen [this message]
2021-10-07 18:49 ` Dave Taht
2021-10-08 17:51 ` Toke Høiland-Jørgensen
2021-10-07 21:39 ` Rich Brown
2021-10-06 21:22 ` Dave Taht
2021-10-06 23:18 ` Jonathan Morton
2021-10-07 0:11 ` Christoph Paasch
2021-10-07 10:29 ` Jonathan Morton
2021-10-07 15:44 ` [Rpm] apple's fq_"codel" implementation Dave Taht
2021-10-07 10:30 ` [Rpm] Alternate definitions of "working condition" - unnecessary? Sebastian Moeller
2021-10-08 0:33 ` Jonathan Morton
2021-10-08 23:32 ` Christoph Paasch
2021-10-11 7:31 ` Sebastian Moeller
2021-10-11 9:01 ` Jonathan Morton
2021-10-11 10:03 ` Sebastian Moeller
2021-10-11 17:34 ` Christoph Paasch
2021-10-12 10:23 ` Sebastian Moeller
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl40n5yv.fsf@toke.dk \
--to=toke@toke.dk \
--cc=jf@jonathanfoulkes.com \
--cc=richb.hanover@gmail.com \
--cc=rpm@lists.bufferbloat.net \
/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