From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave@taht.net>, bloat <bloat@lists.bufferbloat.net>,
cake@lists.bufferbloat.net
Subject: Re: [Bloat] Update Cake page on bufferbloat.net?
Date: Fri, 3 Nov 2017 15:28:19 -0400 [thread overview]
Message-ID: <D690042C-213D-492A-B550-F4327C4126B3@gmail.com> (raw)
In-Reply-To: <878tfnp4sn.fsf@nemesis.taht.net>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
> On Nov 3, 2017, at 2:59 PM, Dave Taht <dave@taht.net> wrote:
>> 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.
>
> where?
This article (https://www.pcmech.com/article/bufferbloat-fix-slow-network/ <https://www.pcmech.com/article/bufferbloat-fix-slow-network/>) is a pretty sub-standard explanation of bufferbloat. But I didn't want to come across as the "smartest (smart-ass) guy in the room"
My plan was to gently correct the worst errors/misperceptions ("it's the bottleneck, stupid") and say that the state of the art had moved ahead, even of fq_codel, then point to the Cake page on the site.
>> But I looked at the Cake page on Bufferbloat.net <http://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/ <https://www.bufferbloat.net/projects/codel/wiki/Cake/>
>
> It's pretty much true.
Good. I will try this weekend to organize that info into a page that would serve well readers like those from the pcmech.com <http://pcmech.com/> site who're new to the subject, and curious about Cake/Bufferbloat.
Rich
[-- Attachment #2: Type: text/html, Size: 4764 bytes --]
next prev parent reply other threads:[~2017-11-03 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 14:53 Rich Brown
2017-11-03 18:59 ` Dave Taht
2017-11-03 19:28 ` Rich Brown [this message]
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=D690042C-213D-492A-B550-F4327C4126B3@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.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