From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: [Bloat] NeST: Network Stack Tester
Date: Fri, 25 Sep 2020 10:25:11 -0700 [thread overview]
Message-ID: <20200925102511.2ded2646@hermes.lan> (raw)
This looks interesting: https://blog.apnic.net/2020/09/18/nest-a-simpleefficient-tool-to-study-congestion-control/
Good - using namespaces for testing is a good idea.
- testbed is GPLv2
Bad - using iperf as your main test tool encourages buffer bloat
- Does 5G really need yet another congestion control algorithm?
Or it this just a way to get the grant money?
Or worse, the start of proprietary TCP congestion control.
next reply other threads:[~2020-09-25 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 17:25 Stephen Hemminger [this message]
2020-09-26 21:24 ` Dave Collier-Brown
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=20200925102511.2ded2646@hermes.lan \
--to=stephen@networkplumber.org \
--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