From: Dave Taht <dave.taht@gmail.com>
To: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: RFC: making sch_cake multicore?
Date: Mon, 31 Jul 2023 12:10:13 -0700 [thread overview]
Message-ID: <CAA93jw6OM9hzT2Okk4_tuLg_f=M-TXz+a17ZrRB2CL9uzm_eig@mail.gmail.com> (raw)
The ongoing, everlasting feature request for CAKE has been to speed it
up on now common multicore embedded hardware. 4 and 8 cores are
increasingly common in my world. I am really out of date on how
feasible this would be, in fact I don't know if older efforts to
remove the locks from pfifo_fast ever succeeded. Similarly, on inbound
shaping, we remain dependent on a tc filter matchall... mirred into
an ifb, which is quite slow and apparently still single threaded.
Leveraging some shared memory area for some shared parameters in a
mqprio-like design is on my mind, but somehow that would have to share
some data with sub-qdiscs.
Over here is a design document talking about two approaches to this so
far. Please comment there. Thx!
https://docs.google.com/document/d/1tTYBPeaRdCO9AGTGQCpoiuLORQzN_bG3TAkEolJPh28/edit#heading=h.1d4d73u2m8nx
--
Podcast: https://www.youtube.com/watch?v=bxmoBr4cBKg
Dave Täht CSO, LibreQos
reply other threads:[~2023-07-31 19:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6OM9hzT2Okk4_tuLg_f=M-TXz+a17ZrRB2CL9uzm_eig@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).