From: Y <intruder_tkyf@yahoo.fr>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] sch_cake shaper/aqm/fq implementation in linux slides and paper
Date: Mon, 29 Apr 2019 11:41:34 +0900 [thread overview]
Message-ID: <20190429114134.6e6360e7@raspberrypi> (raw)
In-Reply-To: <CAA93jw5eU8f7Ldp1-ssHyfO104GOGbQh8m28guTum5KMafoPtw@mail.gmail.com>
It seems Bufferbloat in the world is getting worse.
SAD! :P
Yutaka
Sun, 28 Apr 2019 15:15:44 +0200
Dave Taht <dave.taht@gmail.com> wrote:
> Since sch_cake has been generally available as dual licensed (BSD/GPL)
> open source since last august (as of linux 4.19), and shipping in
> openwrt and evenroute for 3 years, I have generally longed for more
> folk to be fiddling with it in the ietf. The most current stable
> version is in openwrt 18.02, which shipped in january. Cake is in
> general is too complicated and addresses too many things to
> encapsulate into an RFC, but in particular, the DOCSIS/DSL/Ethernet
> framing compensation modes are excellent (unlike the BSD pfsense one),
> and we have many other improvements to multiple components of the SQM
> systems we've been shipping for 8 years. such as per host/per flow FQ,
> sane diffserv support, and ack-filtering being theprimary ones covered
> in slides from my IEEE lanman talk:
>
> http://www.taht.net/~d/sch_cake_ieee_lanman2018%20(2).pdf
>
> One major feature not brought out in paper or slides is that cake
> works the same whether it has backpressure from the device or via
> "BQL", OR in shaping in software. Another important feature -
> GRO-splitting, we haven't gone into much in print yet. In the extra
> slides section are some nice results from a GPON fiber network. It can
> also be used as a local host-only qdisc; there is a brief comparison
> of cake vs sch_fq also in the slides above. As well as in network
> namespaces, vms, docker containers, multi-tenant dcs, etc, etc.
>
> All the features of cake were developed in close collaboration with
> the actual users of SQM in the field.
>
> That paper: https://arxiv.org/pdf/1804.07617.pdf - talks about "Home"
> gateways but since then we got it to scale past 50GigE in software
> alone. I look forward to more independent benchmarkings in other
> scenarios, and we do take bug reports on the github.
>
> Some of the new SCE ("Some Congestion Experienced") related work has
> landed in the https://github.com/dtaht/sch_cake repo already (as well
> as fq_codel_fast) but the majority of work is taking place over in
> jonathan's repos presently.
>
> There is a paper pending, also, on the improvements to codel that
> jonathan (primarily) made in the COBALT AQM that I hope will be
> published soon.
>
> One thing I've longed for is some coherent testing of the modern
> videoconferencing and quic and bbr congestion control algorithms
> against it. Is there anyone out there able to do this and possibly
> collaborate on a paper on it?
>
> I was really quite unaware until this past ietf that so few had had a
> taste of cake yet.
>
> thx!
>
prev parent reply other threads:[~2019-04-29 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 13:15 Dave Taht
2019-04-29 2:41 ` Y [this message]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190429114134.6e6360e7@raspberrypi \
--to=intruder_tkyf@yahoo.fr \
--cc=cake@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