From: Rich Brown <richb.hanover@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Update Cake page on bufferbloat.net?
Date: Fri, 3 Nov 2017 10:53:57 -0400 [thread overview]
Message-ID: <E2173CF2-F8E2-4353-AC52-C29E223AB657@gmail.com> (raw)
Hi folks,
I saw a blog posting that was enthusing about codel/fq_codel, and I was moved to respond that the state of the art was now cake.
But I looked at the Cake page on Bufferbloat.net and wonder if everything there is true, or whether it would be good to update it. https://www.bufferbloat.net/projects/codel/wiki/Cake/
(Once the technical information on that page is current, I would also be willing to tackle a modest reorganization to add some background info to the beginning so that we can cite that page as the primary reference for Cake.)
Thanks!
Rich
next reply other threads:[~2017-11-03 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 14:53 Rich Brown [this message]
2017-11-03 18:59 ` Dave Taht
2017-11-03 19:28 ` Rich Brown
2017-11-03 19:35 ` [Bloat] [Cake] " Jonathan Morton
2017-11-03 19:39 ` Toke Høiland-Jørgensen
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=E2173CF2-F8E2-4353-AC52-C29E223AB657@gmail.com \
--to=richb.hanover@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