From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Alec Robertson <alecrobertson13@gmail.com>,
Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] How to test Cake on TP-Link WDR3600
Date: Sun, 26 Jul 2015 22:05:50 +0100 [thread overview]
Message-ID: <55B54BAE.5000002@gmail.com> (raw)
In-Reply-To: <1437941360960.ed6ad09f@Nodemailer>
On 26/07/15 21:09, Alec Robertson wrote:
> I’ve just updated to the newest trunk release of OpenWRT Chaos Calmer
> (fresh install) and the SQM QOS from OPKG interestingly does include
> Cake as a qdisc but neither layer_cake.qos nor piece_of_cake.qos are
> available as setup scripts.
>
> I’m still trying out Cake so I’ll be back soon with some feedback.
>
You should find the cake option there does nothing?
It'll only work if you have the "kmod-sched-cake" package providing
/lib/modules/*/sch_cake.ko. It's only in Dave's recent experimental builds.
fq_codel is the more supported option and serves the same functions. If
you can notice any difference yet, I think we'd love to hear about it.
Currently I believe the noticeable differences are
1. if your router has TCP offloads enabled, cake undoes ("peels") it
some to improve latency. (Getting this past review for mainline Linux
sounds increasingly "interesting").
2. for networks with many flows, cake works much harder to avoid "hash
collision" (entirely?), so every flow gets a fair share. fq_codel
defaults to 1000 hash buckets (but collision probability will increase
well before that point, see "birthday paradox").
1) seems a real concern for some new routers. If you are affected you
could add a boot script using ethtool.
The idea is it's not optimal to disable offloads universally... maybe if
you're sharing a usb drive from the router as well or something. Having
cake handle it works as a great default configuration. (I just suspect
Linux devs would ask why the feature can't be enabled on other packet
schedulers, e.g. by using a stackable peeler qdisc).
Alan
next prev parent reply other threads:[~2015-07-26 21:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 15:45 Alec Robertson
2015-07-25 16:27 ` Sebastian Moeller
2015-07-25 16:40 ` Alec Robertson
2015-07-25 16:49 ` Alec Robertson
2015-07-25 17:15 ` Sebastian Moeller
2015-07-25 17:38 ` Alec Robertson
2015-07-25 18:12 ` Dave Taht
2015-07-25 18:21 ` Alec Robertson
2015-07-25 18:49 ` Sebastian Moeller
2015-07-25 18:47 ` Sebastian Moeller
2015-07-25 18:57 ` Alec Robertson
2015-07-25 19:19 ` Sebastian Moeller
2015-07-25 20:58 ` Alec Robertson
2015-07-26 7:01 ` Sebastian Moeller
2015-07-26 9:11 ` Alan Jenkins
2015-07-26 12:32 ` Alec Robertson
2015-07-26 12:35 ` Jonathan Morton
2015-07-26 20:09 ` Alec Robertson
2015-07-26 21:05 ` Alan Jenkins [this message]
2015-07-26 21:20 ` Jonathan Morton
2015-07-26 21:38 ` Alan Jenkins
2015-07-27 7:17 ` Sebastian Moeller
2015-08-02 19:04 ` Benjamin Cronce
2015-08-02 20:07 ` Dave Taht
2015-07-27 7:13 ` Sebastian Moeller
2015-07-27 7:10 ` Sebastian Moeller
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=55B54BAE.5000002@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=alecrobertson13@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
/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