From: Thibaut <hacks@slashdirt.org>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Erik Taraldsen via Cake <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Trouble with CAKE
Date: Fri, 13 Dec 2019 23:40:53 +0100 [thread overview]
Message-ID: <E644DF87-72A0-43EC-ABD6-E8E2FAC26997@slashdirt.org> (raw)
In-Reply-To: <6E9587F7-C208-4568-8429-AEBA9E694E24@slashdirt.org>
[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]
> On 13 Dec 2019, at 23:39, Thibaut <hacks@slashdirt.org> wrote:
>
> Hi Jonathan,
>
>> On 13 Dec 2019, at 15:02, Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>>> On 13 Dec, 2019, at 3:43 pm, Thibaut <hacks@slashdirt.org> wrote:
>>>
>>> I've been using CAKE on my DSL-connected Linux router for the last few years, and it worked well until very recently. Two things happened:
>>>
>>> 1) My ISP (French "Free") switched my DSLAM to native IPv6, which for the time being means that I had to revert to using their set-top-box (Freebox) instead of the VDSL2 model I was using in bridge mode until then (CAKE in "bridged-ptm ether-vlan" mode)
>>> 2) I upgraded my router from 3.16 (Devuan Jessie) to 4.9 (Devuan ASCII)
>>>
>>> Since then, no matter which setup I use, I cannot get CAKE to work as intended. Specifically, any long-standing best effort stream (such as a remote rsync) will be throttled to a near grinding halt even though there is no other significant traffic going on. Some random bursts can be seen (with iftop) but nothing ever gets close to half the maximum bandwidth. This is notably affecting the OpenWRT buildbots I'm hosting on this link.
>>
>> Old kernels, including 4.9 series, tend to be more problematic than the latest ones. If you can, I would recommend updating to a 5.x series kernel, in which Cake is an upstream feature. I won't presume to guess how best to achieve that with your distro.
>
> I’m now able to confirm this looks like a regression: I was able to retrieve and build the last known working version of CAKE on my router, and with an adjusted overhead of 48 atm (confirmed thanks to the help of Stephan), it works like a charm. Current HEAD doesn’t, with the exact same parameters.
I meant Sebastian, sorry. And this is old CAKE running on distro 4.9, for the sake of clarity
Thibaut
[-- Attachment #2: Type: text/html, Size: 5110 bytes --]
next prev parent reply other threads:[~2019-12-13 22:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 13:43 Thibaut
2019-12-13 14:02 ` Jonathan Morton
2019-12-13 22:39 ` Thibaut
2019-12-13 22:40 ` Thibaut [this message]
2019-12-13 23:52 ` Thibaut
2019-12-14 9:50 ` Jonathan Morton
2019-12-14 10:01 ` Thibaut
2019-12-14 10:35 ` Kevin 'ldir' Darbyshire-Bryant
2019-12-14 10:56 ` Kevin 'ldir' Darbyshire-Bryant
2019-12-14 11:59 ` Thibaut
2019-12-14 12:07 ` Thibaut
2019-12-14 12:09 ` Jonathan Morton
2019-12-14 12:11 ` Thibaut
2019-12-14 12:59 ` Toke Høiland-Jørgensen
2019-12-14 14:04 ` Thibaut
2019-12-14 21:35 ` Toke Høiland-Jørgensen
2019-12-13 14:13 ` Thibaut
2019-12-13 14:15 ` Sebastian Moeller
2019-12-13 14:21 ` Thibaut
2019-12-13 18:44 ` Thibaut
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=E644DF87-72A0-43EC-ABD6-E8E2FAC26997@slashdirt.org \
--to=hacks@slashdirt.org \
--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