From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dan Siemon <dan@coverfire.com>, Dave Taht <dave.taht@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Using cake to shape 1000’s of users.
Date: Fri, 27 Jul 2018 00:38:13 +0300 [thread overview]
Message-ID: <C3698A0F-E35B-478B-BA7C-8CFEAE245D65@gmail.com> (raw)
In-Reply-To: <87tvol1z6h.fsf@toke.dk>
> On 27 Jul, 2018, at 12:09 am, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>>>> I haven't had time to try Cake in this context yet but hope to get to
>>>> that in the next couple months. I believe this will require one Cake
>>>> instance per-subscriber like we do with FQ-CoDel today.
>>>
>>> Yup, currently it would. It might be possible to extend CAKE's
>>> architecture to not require this, though. If you are interested in
>>> pursuing this in the future, let us know; having someone actually
>>> using it would be quite useful if we were to pursue development of this :)
>>
>> Yes, I'm very interested in this. A single QDisc would simplify things
>> quite a bit and hopefully be a perf win.
>>
>> I'm happy to test this locally and with real subscribers once it is
>> stable enough.
>
> Cool. No promises as to when (or even if) I get around to looking at
> this; but will ping you when/if I do :)
Alternatively, I could look into it. I have time, but funding would be nice. Perhaps if several organisations have some commercial interest in the idea, they could pool some resources to keep my fridge stocked and a roof over my head?
It would also be valuable to have a firmer handle on the actual requirements in the field. For example, if it is feasible to focus only on current Linux kernels, then a lot of backwards compatibility cruft can be excised when importing existing code from Cake. If all users will have the same link-layer technology (with the same overhead parameters), then these can be set globally - or if not, they can be set per-tier. Is the Diffserv support from Cake likely to be useful, and if so how flexible should the configuration be? And are there only a few discrete settings for bandwidth per user, or do we have to be more flexible to handle a BRAS environment? Is it also necessary to account per-user traffic accurately, or will an external tool be used for that?
Many other low-level considerations can be adjusted on the fly during the conversion, so they are not in themselves a problem. In this category are questions like "how many simultaneous users and flows can be supported". There are ways to design the code so that it scales up much more nicely in these dimensions than Cake does, at the expense of a few extra CPU cycles per packet.
- Jonathan Morton
next prev parent reply other threads:[~2018-07-26 21:38 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 7:24 Felix Resch
2018-07-17 16:59 ` Dave Taht
2018-07-26 15:46 ` Dan Siemon
2018-07-26 15:48 ` Dave Taht
2018-07-26 18:07 ` Dan Siemon
2018-07-28 15:51 ` Dave Taht
2018-07-28 16:11 ` Jonathan Morton
2018-07-28 16:36 ` Dave Taht
2018-07-26 17:42 ` Toke Høiland-Jørgensen
2018-07-26 18:10 ` Dan Siemon
2018-07-26 21:09 ` Toke Høiland-Jørgensen
2018-07-26 21:38 ` Jonathan Morton [this message]
2018-07-27 9:25 ` Pete Heist
2018-07-27 14:04 ` Dan Siemon
2018-07-27 18:58 ` Jonathan Morton
2018-07-28 8:56 ` Toke Høiland-Jørgensen
2018-07-28 15:04 ` Dave Taht
2018-07-28 16:19 ` Jonathan Morton
2018-07-28 16:39 ` Dave Taht
2018-07-28 17:01 ` Pete Heist
2018-07-28 17:37 ` Pete Heist
2018-07-28 17:52 ` Dave Taht
2018-07-28 17:56 ` Dave Taht
2018-07-28 18:12 ` Toke Høiland-Jørgensen
2018-07-29 0:17 ` Pete Heist
2018-07-29 19:14 ` Toke Høiland-Jørgensen
2018-07-30 9:14 ` Pete Heist
2018-07-30 10:09 ` Sebastian Moeller
2018-07-30 10:55 ` Toke Høiland-Jørgensen
2018-07-30 11:05 ` Pete Heist
2018-07-30 11:28 ` Toke Høiland-Jørgensen
2018-07-30 22:10 ` Pete Heist
2018-07-30 22:17 ` Toke Høiland-Jørgensen
2018-07-31 7:31 ` Jonathan Morton
2018-07-30 10:55 ` Pete Heist
2018-07-30 11:05 ` Jonathan Morton
2018-07-28 17:53 ` Jonathan Morton
2018-07-28 18:07 ` Dave Taht
2018-07-28 18:17 ` Toke Høiland-Jørgensen
2018-07-28 19:35 ` [Cake] 1000s " Dave Taht
2018-07-29 23:24 ` [Cake] Using cake to shape 1000’s " Dave Taht
2018-08-07 1:46 ` Dan Siemon
2018-07-28 7:18 ` Pete Heist
2018-07-28 8:06 ` Jonathan Morton
2018-07-28 16:41 ` Pete Heist
2018-07-28 17:32 ` [Cake] isp economics Dave Taht
2018-07-28 18:39 ` Pete Heist
2018-07-28 19:03 ` Dave Taht
2018-07-28 20:00 ` Pete Heist
2018-07-29 5:49 ` Loganaden Velvindron
2018-07-28 19:09 ` Dave Taht
-- strict thread matches above, loose matches on Subject: below --
2018-07-16 18:39 [Cake] Using cake to shape 1000’s of users Mike
2018-07-16 19:01 ` Jonathan Morton
2018-07-16 19:13 ` Michel Blais
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=C3698A0F-E35B-478B-BA7C-8CFEAE245D65@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dan@coverfire.com \
--cc=dave.taht@gmail.com \
--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