From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Klatsky, Carl" <Carl_Klatsky@comcast.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Netperf re-licensed as MIT
Date: Mon, 29 Mar 2021 11:25:55 -0700 [thread overview]
Message-ID: <CALQXh-N8UC5JdhO=dSbPkTYFJ1GR-3mL5qh4MsPRLVOpXxBH=A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7tKkMfsNPUwfFhVZePAtiSNhH-0rT7G+pZR3C90D3AFw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2940 bytes --]
iperf3 isn’t “academic”, but is more focused on scientific computing (ESNet
pushes a LOT of data CERN around, on 100Gbps backbones).
But that also skews their usage/needs. Very high throughput bulk transfers
with long durations, over mixed systems. Not as many concerns about
latency, except in that latency can cause messes with congestion control.
On Sat, Mar 27, 2021 at 2:45 PM Dave Taht <dave.taht@gmail.com> wrote:
> so glad to hear the license has been fixed.
>
> carl, iperf is only used in a few of flent's tests. We trusted netperf
> - as did the linux kernel developers - a lot further than all the
> iperf variants combined - at the time we started work on flent.
>
> I would not mind us somehow developing a drop in replacement for
> netperf, perhaps leveraging the irtt codebase, as I have a long
> standing desire to be able to reliably measure latencies and the
> output of TCP_INFO in "some" tool below 250us.
>
> iperf has come a long way, but getting to where I could trust the
> largely "academic" codebase it was would take a ton of benchmarking.
>
> On Sat, Mar 27, 2021 at 2:09 PM Klatsky, Carl via Bloat
> <bloat@lists.bufferbloat.net> wrote:
> >
> > 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$
> > _______________________________________________
> > Bloat mailing list
> > Bloat@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
> "For a successful technology, reality must take precedence over public
> relations, for Mother Nature cannot be fooled" - Richard Feynman
>
> dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
- Sent from my iPhone.
[-- Attachment #2: Type: text/html, Size: 4507 bytes --]
next prev parent reply other threads:[~2021-03-29 18:26 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
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 [this message]
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='CALQXh-N8UC5JdhO=dSbPkTYFJ1GR-3mL5qh4MsPRLVOpXxBH=A@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=Carl_Klatsky@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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