From: "Klatsky, Carl" <Carl_Klatsky@comcast.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Netperf re-licensed as MIT
Date: Sat, 27 Mar 2021 21:08:54 +0000 [thread overview]
Message-ID: <MN2PR11MB46648F5E6F759954EEE28104A6609@MN2PR11MB4664.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87pmzla3vw.fsf@toke.dk>
Toke,
How you see this coming into Flent? My understanding is that for latency & load test like RRUL:
-iperf provides the bandwidth portion
-IRTT provides the latency portion, and if IRTT is not found, the test falls back to ICMP for the latency check
Would netperf replace iperf for the bandwidth portion? Do you see it being used for the latency portion?
Thanks,
Carl
-----Original Message-----
From: Bloat <bloat-bounces@lists.bufferbloat.net> On Behalf Of Toke Høiland-Jørgensen via Bloat
Sent: Friday, March 26, 2021 7:32 PM
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Netperf re-licensed as MIT
Hopefully this means we can get it packaged for the distros that have thus far refused to because of the license - i.e., Debian and Fedora!
-Toke
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!W_yWwnGSD6VuZvpn0BPv7Ta9GBP3f2dRWeJHPLS7RrrpBZ5gpyj5DZGnRYIfWVR5TXjR$
next prev parent reply other threads:[~2021-03-27 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 23:31 Toke Høiland-Jørgensen
2021-03-27 21:08 ` Klatsky, Carl [this message]
2021-03-27 21:44 ` Dave Taht
2021-03-27 21:45 ` Dave Taht
2021-03-29 18:29 ` Aaron Wood
2021-03-29 18:38 ` Dave Taht
2021-03-29 19:37 ` Toke Høiland-Jørgensen
2021-03-28 20:47 ` Toke Høiland-Jørgensen
2021-03-29 18:25 ` Aaron Wood
2021-03-29 19:38 ` 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=MN2PR11MB46648F5E6F759954EEE28104A6609@MN2PR11MB4664.namprd11.prod.outlook.com \
--to=carl_klatsky@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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