From: Jonathan Morton <chromatix99@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Thinking about ingress shaping & cake
Date: Fri, 10 Apr 2020 17:14:51 +0300 [thread overview]
Message-ID: <B37EB18D-CA01-464B-8924-7864FE9A327E@gmail.com> (raw)
In-Reply-To: <7BD9FB5D-7577-477A-9FF0-7BF90043C27B@darbyshire-bryant.me.uk>
> On 10 Apr, 2020, at 4:16 pm, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>
> I have a 80/20mbit FTTC line into the house. Egress shaping/control with cake is simple, easy, beautiful and it works. Tell it to use 19900Kbit, set some min packet size, a bit of overhead and off you go. Ingress has more problems:
>
> Assuming I do actually get 80Mbit incoming then the naive bandwidth setting for CAKE would be 80Mbit. Cake internally dequeues at that 80Mbit rate and therefore the only way any flows can accumulate backlog is when they’re competing with each other in terms of fairness(Tin/Host) and quantums become involved…I think.
No. If the dequeue rate is never less than the enqueue rate, then the backlog remains at zero pretty much all the time. There are some short-term effects which can result in transient queuing of a small number of packets, but these will all drain out promptly.
For Cake to actually gain control of the bottleneck queue, it needs to *become* the bottleneck - which, when downstream of the nominal bottleneck, can only be achieved by shaping to a slower rate. I would try 79Mbit for your case.
- Jonathan Morton
next prev parent reply other threads:[~2020-04-10 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 13:16 Kevin Darbyshire-Bryant
2020-04-10 14:14 ` Jonathan Morton [this message]
2020-04-12 8:23 ` Kevin Darbyshire-Bryant
2020-04-12 9:47 ` Sebastian Moeller
2020-04-12 11:02 ` Jonathan Morton
2020-04-12 13:12 ` Kevin Darbyshire-Bryant
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=B37EB18D-CA01-464B-8924-7864FE9A327E@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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