From: Sebastian Moeller <moeller0@gmx.de>
To: Alex Garrood <agarrood25@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] LEDE project - piece_of_cake or layer_cake QOS script
Date: Sat, 29 Oct 2016 22:40:18 +0200 [thread overview]
Message-ID: <1CA473B3-37B5-4E77-A049-C30FCA12EAD1@gmx.de> (raw)
In-Reply-To: <CALMNQQoJjoiNByFF7PGj2Rju7Peokx+jH2GsprWuDufvMB-drQ@mail.gmail.com>
Hi Alex,
> On Oct 29, 2016, at 16:17, Alex Garrood <agarrood25@gmail.com> wrote:
>
> Hi all, I've just flashed a LEDE image to my home router in order to
> make use of Cake.
>
> I noticed there are two different Queue setup scripts in luci-app-sqm:
>
> layer_cake.qos:
> This uses the cake qdisc as a replacement for htb as shaper and
> fq_codel as leaf qdisc. This exercises cake's diffserv profile(s) as
> different "layers" of priority. This script requires that cake is
> selected as qdisc.
>
> piece_of_cake.qos:
> This just uses the cake qdisc as a replacement for htb as shaper and
> fq_codel as leaf qdisc. It just does not come any simpler than this,
> in other words it truely is a "piece of cake". This script requires
> that cake is selected as qdisc.
>
>
> Which would you recommend for a home network type setup and are there
> any particular advantages or disadvantages to either option?
So do you use DSCP to selectively mark the “priority” of packets? If yes you might want to look at layer-cake. Do you really want the computationally cheapest* way to solve your generalized shaping needs have a look at piece-of-cake. For most users I assume that piece-of-cake should be fine. That said, sqm-scripts could do abetter job at exposing cake’s specific options, but since I have lost my faith in cake’s speedy upstreaming I am kind of hesitant to add options to luci-app-sqm that might not survive the contact with linux kernel, and I absolutely detest the unholy non-systematic mess that cake’s overhead accounting options turned into… (and there are ways in the GUI to pass un-checked strings of options to the under laying qdisc’s already).
Best Regards
Sebastian
>
> Many thanks.
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
prev parent reply other threads:[~2016-10-29 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 14:17 Alex Garrood
2016-10-29 20:40 ` Sebastian Moeller [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=1CA473B3-37B5-4E77-A049-C30FCA12EAD1@gmx.de \
--to=moeller0@gmx.de \
--cc=agarrood25@gmail.com \
--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