From: Dave Collier-Brown <dave.collier-brown@indexexchange.com>
To: bloat@lists.bufferbloat.net, stephen@networkplumber.org
Subject: Re: [Bloat] NeST: Network Stack Tester
Date: Sat, 26 Sep 2020 17:24:57 -0400 [thread overview]
Message-ID: <32e040a8-bf2b-33d9-c024-e8f11d1e69b9@indexexchange.com> (raw)
In-Reply-To: <20200925102511.2ded2646@hermes.lan>
Making things easy to test is good, and I generally assume anything said
about 5G is marketing (three drink minimum (;-))
Academics often respond positively to opportunities to make their
metrics better, so we might want to write to them and suggest some valid
follow-on work... to apply for grants for.
Drop me a line if you would like to do so.
--dave
On 2020-09-25 1:25 p.m., Stephen Hemminger wrote:
> 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.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
dave.collier-brown@indexexchange.com | -- Mark Twain
CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory.
prev parent reply other threads:[~2020-09-26 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 17:25 Stephen Hemminger
2020-09-26 21:24 ` Dave Collier-Brown [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=32e040a8-bf2b-33d9-c024-e8f11d1e69b9@indexexchange.com \
--to=dave.collier-brown@indexexchange.com \
--cc=bloat@lists.bufferbloat.net \
--cc=stephen@networkplumber.org \
/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