From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave@taht.net>, Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] signed-off-by requests
Date: Thu, 23 Nov 2017 13:55:54 -0800 [thread overview]
Message-ID: <CAA93jw4Vxm89k7coUD_xQTkt0LW+TAh9s32Sier1hifPkT19+Q@mail.gmail.com> (raw)
If anyone wants to add a signed-of-by, acked-by, or tested-by to the
next patchset let me know.
On Tue, Nov 21, 2017 at 11:46 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Dave Taht <dave@taht.net> writes:
>
>> And now I can comment.
>>
>> I've added this version to a for_upstream branch in the hope that future
>> commits can be kept in sync.
>>
>> Is there anything more that should be added to the commit message?
>> Should I be less snarky?
>>
>>> while presenting an API simple enough that even an ISP can configure
>>> it.
>
> I chuckled at this part at least. I'd say keep it ;)
>
>>> Example of use on an ISP uplink:
>>>
>>> tc qdisc add dev eth0 cake bandwidth 20Mbit nat docsis ack-filter
>>>
>>> Cake can also be used in unlimited mode to drive packets at the speed
>>> of the underlying link.
>>>
>>> Cake is filled with:
>>>
>>> * A hybrid Codel/Blue AQM algorithm, “Cobalt”, tied to an FQ_Codel
>>> derived Flow Queuing system, which autoconfigures based on the bandwidth.
>>> * A unique "triple-isolate" mode (the default) which balances per-flow
>>> and per-host flow FQ even through NAT.
>>> * An integral deficit based shaper with extensive dsl and docsis support
>>> that can also be used in unlimited mode.
>
> "dsl and docsis link layer compensation support"? Not sure someone
> who hasn't drunk the koolaid understands how a shaper can have "dsl and
> docsis support"
>
>>> * 8 way set associative queuing to reduce flow collisions to a
>>>minimum.
>
> 8-way set-associative hashing
>
>>> * A reasonable interpretation of various diffserv latency/loss
>>>tradeoffs.
>
> Heh. Not sure the word 'reasonable' can reasonably be applied to
> diffserv ;)
>
>>> * Support for washing diffserv for entering and exiting traffic.
>
> The term 'washing' is also internal; explain it? ("washing (zeroing)
> diffserv markings")
>
>>> * Perfect support for interacting with Docsis 3.0 shapers.
>
> What does that mean?
>
>>> * Extensive support for DSL framing types.
>
> Aren't you just repeating yourself from above now?
>
>>> * (New) Support for ack filtering.
>>> - 20 % better throughput at a 16x1 down/up ratio on the rrul test.
>
> From the PoV of an upstream submission it's all new, isn't it? Also,
> this is the only place where you cite benchmark results.
>
>>> * Extensive statistics for measuring, loss, ecn markings, latency variation.
>>>
>>> There are some features still considered experimental, notably the
>>> ingress_autorate bandwidth estimator and cobalt itself.
>>>
>>> Various versions shipping have been available as an out of tree build for
>>> kernel versions going back to 3.10, as the embedded router world has been
>>> running a few years behind mainline Linux. A stable version has been
>>> generally available on lede-17.01 and later.
>>>
>>> sch_cake replaces a combination of iptables, tc filter, htb and fq_codel in
>>> the sqm-scripts, with sane defaults and vastly easier configuration.
>
> s/easier/simpler/
>
>>> Cake's principal author is Jonathan Morton, with contributions from
>>> Kevin Darbyshire-Bryant, Toke Høiland-Jørgensen, Sebastian Moeller,
>>> Ryan Mounce, Dean Scarff, Guido Sarducci, Nils Andreas Svee, Dave Täht, and
>>> Loganaden Velvindron.
>
> But no Signed-off-by? :)
>
>
> -Toke
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next reply other threads:[~2017-11-23 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 21:55 Dave Taht [this message]
2017-11-23 23:06 ` Jonathan Morton
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=CAA93jw4Vxm89k7coUD_xQTkt0LW+TAh9s32Sier1hifPkT19+Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=toke@toke.dk \
/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