[Bloat] Update Cake page on bufferbloat.net?

[Bloat] Update Cake page on bufferbloat.net?

[Rich Brown]

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

Re: [Bloat] Update Cake page on bufferbloat.net?

[Dave Taht]

Rich Brown <richb.hanover@gmail.com> writes:

> 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.

where?

> 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/

It's pretty much true.

> (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.)

I would really for us to make the effort to upstream this in 2018. I'm
still dubious about "cobalt", and I'd like to make the GRO peeling less
agressive (again), relative to load, and it needs some cleanups to match
current kernels.

>
> Thanks!
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

Re: [Bloat] Update Cake page on bufferbloat.net?

[Rich Brown]

[-- 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 --]

Re: [Bloat] [Cake] Update Cake page on bufferbloat.net?

[Jonathan Morton]

[-- Attachment #1: Type: text/plain, Size: 103 bytes --]

I think "mostly true but incomplete" is the best way to describe the
current pages.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 152 bytes --]

Re: [Bloat] [Cake] Update Cake page on bufferbloat.net?

[Toke Høiland-Jørgensen]

Jonathan Morton <chromatix99@gmail.com> writes:

> I think "mostly true but incomplete" is the best way to describe the
> current pages.

Patches welcome :)

https://github.com/tohojo/bufferbloat-net

-Toke