From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] fq_codel wikipedia page in progress
Date: Mon, 15 Nov 2021 08:40:44 -0800 [thread overview]
Message-ID: <CAA93jw6Sc5zF7SctTETfo_RpJ5NuA38ivoHf75Tj4_SqgDzcwg@mail.gmail.com> (raw)
OK, I finally bit the bullet and started editing wikipedia for the
first time, seriously. That said, i have very little patience for it,
especially cite hunting. It's taken me, what? 8 years to attempt this.
There's an awful lot on wikipedia that needs improvement elsewhere
also.
https://en.wikipedia.org/wiki/FQ_CODEL
I'm especially looking for, under an appropriate license:
* A good graph that shows how DRR uses bytes of multiple packets
rather than SFQ-like packets
Having some sort of sequence of graphs that shows how codel does a
timestamp and looks at it would be good. The *only* thing I've ever
developed for this was in my stanford talk....
Also:
* More cites and pointers to existing source code for fq_codel (wasn't
there a dpdk version?)
* Confirmation on the web on where and in what products its used in
* Academic references
* Benchmarks
* Sample output from each of the OS's equivalents of the tc -s qdisc
show command
And of course to generate the worlds most perfect explanation as to
how and why it works.
Other someday targets of a writing stint might be flent, the rrul
test, the networkquality test, smart queue management, the list goes
on and on.
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2021-11-15 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:40 Dave Taht [this message]
2021-11-15 22:15 ` Kenneth Porter
2021-11-15 22:47 ` Kenneth Porter
2021-11-16 17:57 ` Jan Ceuleers
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=CAA93jw6Sc5zF7SctTETfo_RpJ5NuA38ivoHf75Tj4_SqgDzcwg@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