netdev - RFC: is sch_cake fully baked?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Tue, 23 Nov 2021 18:48:38 -0800
From:   Dave Taht <dave.taht@...il.com>
To:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: RFC: is sch_cake fully baked?

Since its incorporation in linux mainline a few years ago sch_cake has
been migrating into various other niches, like mikrotik, and finding
new uses in middleware outside our original home gateway intent.

The feature set has been stable a long while, aside from ongoing
experimentation with L4S and SCE. It's been great to leverage
continued improvements in the flow dissector in particular.

Our biggest end-user request has been to speed it up somehow,
especially for inbound shaping. The most frequent suggestion on that
front is to somehow make it multi-core, but no-one in the cake team
knows how to do that. Other means of speeding it up, like using XPF
and XDP, have recently appeared in things like
https://github.com/rchac/LibreQoS .

If anyone has thoughts for sch_cake's future, please hit
https://forum.openwrt.org/t/making-cake-multicore-or-other-new-features/112623

with suggestions?

Thx!

-- 
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org

Dave Täht CEO, TekLibre, LLC