From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Sebastian Moeller <moeller0@gmx.de>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] CAKE in openwrt high CPU
Date: Tue, 1 Sep 2020 22:05:21 +0300 [thread overview]
Message-ID: <48FC5B6D-21B6-4A5E-88DC-18FF03BE47C0@gmail.com> (raw)
In-Reply-To: <87o8mpibew.fsf@toke.dk>
> On 1 Sep, 2020, at 9:45 pm, Toke Høiland-Jørgensen via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> CAKE takes the global qdisc lock.
Presumably this is a default mechanism because CAKE doesn't handle any locking itself.
Obviously it would need to be replaced with at least a lock over CAKE's complete data structures, taking the lock on each entry point and releasing it at each return point, and I assume there is a flag we can set to indicate we do so. Finer-grained locking might be possible, but CAKE is fairly complex so that might be hard to implement. Locking per CAKE instance would at least allow running ingress and egress on different CPUs.
Is there an example anywhere on how to do this?
- Jonathan Morton
next prev parent reply other threads:[~2020-09-01 19:05 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 [this message]
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
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=48FC5B6D-21B6-4A5E-88DC-18FF03BE47C0@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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