From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Luca Muscariello <muscariello@ieee.org>,
Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] CAKE in openwrt high CPU
Date: Thu, 03 Sep 2020 16:32:41 +0200 [thread overview]
Message-ID: <877dtbgcc6.fsf@toke.dk> (raw)
In-Reply-To: <CAH8sseTmFM0xiHqg_EyD-3bPaCFCfsFOkM4HB8-XtOL0YZQr7g@mail.gmail.com>
Luca Muscariello <muscariello@ieee.org> writes:
> On Thu, Sep 3, 2020 at 3:19 PM Mikael Abrahamsson via Bloat
> <bloat@lists.bufferbloat.net> wrote:
>>
>> On Tue, 1 Sep 2020, Toke Høiland-Jørgensen wrote:
>>
>> > Yup, the number of cores is only going to go up, so for CAKE to stay
>> > relevant it'll need to be able to take advantage of this eventually :)
>>
>> https://www.hardkernel.com/shop/odroid-h2plus/ is an interesting platform,
>> it has a quad core machine with 2 x 2.5GbE NICs.
>>
>> When using something like this for routing with HTB+CAKE for bidirectional
>> shaping below line rate, what would be the main things that would need to
>> be improved?
>
> IMO, hardware offloading for shaping, beyond this specific platform.
> I ignore if there is any roadmap with that objective.
Yeah, offloading of some sort is another option, but I consider that
outside of the "CAKE stays relevant" territory, since that will most
likely involve an entirely programmable packet scheduler. There was some
discussion of adding such a qdisc to Linux at LPC[0]. The Eiffel[1]
algorithm seems promising.
-Toke
[0] https://linuxplumbersconf.org/event/7/contributions/679/
[1] https://www.usenix.org/conference/nsdi19/presentation/saeed
next prev parent reply other threads:[~2020-09-03 14:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 17:27 Mikael Abrahamsson
2020-08-30 17:52 ` Dave Taht
2020-08-31 11:35 ` Toke Høiland-Jørgensen
2020-08-31 12:22 ` Mikael Abrahamsson
2020-08-31 13:29 ` Toke Høiland-Jørgensen
2020-09-03 13:10 ` Mikael Abrahamsson
2020-09-03 13:29 ` Toke Høiland-Jørgensen
2020-09-03 13:34 ` Sebastian Moeller
2020-09-03 13:32 ` Sebastian Moeller
2020-09-04 13:37 ` Mikael Abrahamsson
2020-09-04 14:12 ` Sebastian Moeller
2020-09-01 15:41 ` Jonathan Foulkes
2020-09-01 16:11 ` Toke Høiland-Jørgensen
2020-09-01 16:25 ` Sebastian Moeller
2020-09-01 18:45 ` Toke Høiland-Jørgensen
2020-09-01 19:05 ` Jonathan Morton
2020-09-01 21:09 ` Toke Høiland-Jørgensen
2020-09-01 19:01 ` Jonathan Foulkes
2020-09-01 21:11 ` Toke Høiland-Jørgensen
2020-09-02 20:26 ` Jonathan Foulkes
2020-09-02 20:57 ` Toke Høiland-Jørgensen
2020-09-03 13:19 ` Mikael Abrahamsson
2020-09-03 13:27 ` Luca Muscariello
2020-09-03 14:32 ` Toke Høiland-Jørgensen [this message]
2020-09-03 15:31 ` Luca Muscariello
2020-09-03 18:39 ` Toke Høiland-Jørgensen
2020-09-03 18:53 ` Jonathan Morton
2020-09-03 22:14 ` [Bloat] Other CAKE territory (was: CAKE in openwrt high CPU) David Collier-Brown
2020-09-04 1:19 ` Jonathan Morton
2020-09-04 13:41 ` Mikael Abrahamsson
2020-09-04 11:11 ` Toke Høiland-Jørgensen
2020-09-03 13:27 ` [Bloat] CAKE in openwrt high CPU Toke Høiland-Jørgensen
2020-09-01 16:18 ` Sebastian Moeller
2020-09-01 19:31 ` Jonathan Foulkes
2020-09-01 20:04 ` Sebastian Moeller
2020-09-01 20:09 ` Jonathan Morton
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dtbgcc6.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=muscariello@ieee.org \
--cc=swmike@swm.pp.se \
/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