From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] wanted: additional examples of networking bugs "found with flent"
Date: Sat, 11 Feb 2017 14:14:00 -0800 [thread overview]
Message-ID: <CAA93jw6Xw6yma0iVdoVob8z2a8rHA2Z8ZXL9vyGKDoUR2S9oBw@mail.gmail.com> (raw)
I've long had a piece in draft that talks about the kind of network
problems we've diagnosed using flent to generate the results.
The draft is polished up and mostly read here:
https://github.com/dtaht/blog-cerowrt/blob/master/content/post/found_in_flent.md
(or just clone the repo and run hugo on it)
I am curious if anyone else here has examples and the test data for
another bug found by using flent that I can add to this piece?
There's a companion piece (flaws in flent), that is getting closer to
completion also (it's still a bit too ranty), and I needed to get both
of these out of my system in order to write a more basic tutorial,
next.
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
reply other threads:[~2017-02-11 22:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw6Xw6yma0iVdoVob8z2a8rHA2Z8ZXL9vyGKDoUR2S9oBw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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