From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Aaron Wood <woody77@gmail.com>, Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Netperf re-licensed as MIT
Date: Mon, 29 Mar 2021 21:38:55 +0200 [thread overview]
Message-ID: <878s65sqb4.fsf@toke.dk> (raw)
In-Reply-To: <CALQXh-N8UC5JdhO=dSbPkTYFJ1GR-3mL5qh4MsPRLVOpXxBH=A@mail.gmail.com>
Aaron Wood <woody77@gmail.com> writes:
> 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.
Yeah, I'm not too concerned about the code quality of iperf either - if
it ever reaches (rough) feature parity with netperf (list I posted
up-thread) I'm quite happy to turn it into an automatic fallback for
netperf in Flent, the same way we do with some of the other tools...
-Toke
prev parent reply other threads:[~2021-03-29 19:38 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
2021-03-29 19:38 ` 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=878s65sqb4.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=woody77@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