From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Pete Heist <pete@eventide.io>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Pre-print of Cake paper available
Date: Tue, 24 Apr 2018 11:38:24 +0200 [thread overview]
Message-ID: <4889B2A7-331E-4513-A985-120B21876B8E@gmx.de> (raw)
In-Reply-To: <87d0yp7xyn.fsf@toke.dk>
Hi Toke,
> On Apr 24, 2018, at 11:30, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Sebastian Moeller <moeller0@gmx.de> writes:
> [...]
>>>
>>> I don't think we can make assumptions on ISP deployments.
>>
>> Sure we do not really need to:
>> https://forum.lede-project.org/t/transparent-cake-box/2161/4?u=moeller0
>> and
>> https://forum.lede-project.org/t/lede-as-a-dedicated-qos-bufferbloat-appliance/1861/14?u=moeller0
>> so it looks like one person already use cake in an small ISP context.
>> Now 1 is not a very convincing number, but certainly larger than
>> zero...
>
> Well I just meant that there are many ways to deploy a shaper in an ISP
> context (centrally in the network, at the next hop from the customer,
> etc).
Ah, sorry, I fully agree; and if ISPs are interested they should start talking; I just wanted to report the one case where cake seems to be used in an ISP-ish context.
>
> Looking at those threads, they seem to be increasing the number of
> queues. Not sure they need to, but, well, there's nothing in principle
> that says this couldn't be configurable (it is in FQ-CoDel). It would
> need a bit of a reorg of the current code, though, so that would be a
> thing for later I guess...
I had hoped that orangetek could be convinced to do measurements with different number of queues to answer that question, but I guess the current default of 1000 queues is decent for a typical homenet, but will simply become a bit tight with 600 concurrent households (I assume that its the peak usage that would want more queues on the "back-haul", on average 1000 might still be okay, especially with Jonathan's clever set associativity design)
Best Regards
Sebastian
>
> -Toke
next prev parent reply other threads:[~2018-04-24 9:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 8:39 Toke Høiland-Jørgensen
2018-04-23 9:54 ` Jonathan Morton
2018-04-23 23:01 ` Pete Heist
2018-04-23 23:31 ` Jonathan Morton
2018-04-24 5:44 ` Pete Heist
2018-04-24 5:58 ` Jonathan Morton
2018-04-24 7:15 ` Pete Heist
2018-04-24 7:56 ` Sebastian Moeller
2018-04-24 8:45 ` Toke Høiland-Jørgensen
2018-04-24 8:57 ` Pete Heist
2018-04-25 18:44 ` David Lang
2018-04-25 20:28 ` Toke Høiland-Jørgensen
2018-04-26 19:27 ` Pete Heist
2018-04-27 11:08 ` Toke Høiland-Jørgensen
2018-04-27 11:20 ` Pete Heist
2018-04-24 8:17 ` Sebastian Moeller
2018-04-24 8:47 ` Toke Høiland-Jørgensen
2018-04-24 8:50 ` Jonathan Morton
2018-04-24 9:06 ` Pete Heist
2018-04-24 9:15 ` Toke Høiland-Jørgensen
2018-04-24 9:36 ` Pete Heist
2018-04-24 9:18 ` Sebastian Moeller
2018-04-24 9:30 ` Toke Høiland-Jørgensen
2018-04-24 9:38 ` Sebastian Moeller [this message]
2018-04-24 9:44 ` Toke Høiland-Jørgensen
2018-04-24 15:08 ` John Yates
2018-04-24 8:43 ` Toke Høiland-Jørgensen
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=4889B2A7-331E-4513-A985-120B21876B8E@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=pete@eventide.io \
--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