From: Stephen Hemminger <stephen@networkplumber.org>
To: dave seddon <dave.seddon.ca@gmail.com>
Cc: Frantisek Borsik <frantisek.borsik@gmail.com>,
Cake List <cake@lists.bufferbloat.net>,
codel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>,
Jeremy Austin via Rpm <rpm@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
ryan@rkhtech.org
Subject: [Rpm] Re: [Bloat] Re: [Cake] CAKE-MQ merged to OpenWrt 25.12 today (February 15)
Date: Mon, 16 Feb 2026 22:41:31 -0800 [thread overview]
Message-ID: <20260216224131.5c5ae855@phoenix.local> (raw)
In-Reply-To: <CANypexSO1MfHT2Qpf9YcNBtnV6OuZD9F8Db_EEkFKga=S176CA@mail.gmail.com>
On Mon, 16 Feb 2026 22:10:31 -0800
dave seddon <dave.seddon.ca@gmail.com> wrote:
> Woot woot!
>
> Thanks for the mq-cake patches. !
>
> I got them working on NixOS 6.12 ( and next-net patches on 6.18.8 )
>
> [das@l2:~/nixos/desktop/l2/mq-cake-orchestrator]$ uname -a
> Linux l2 6.12.68 #1-NixOS SMP PREEMPT_DYNAMIC Fri Jan 30 09:28:49 UTC
> 2026 x86_64 GNU/Linux
>
>
> I'm currently setting up a load-testing harness. The idea will be to
> generate MANY 5-tuple flows to really stress out the qdiscs
>
> Early results, but they look great!
How fast is the CPU, because on current Arm Cortex-A53 cake is cpu
limited and max's out around 500Mbps but can do fq-codel at 900.
Could be fixed by tuning?
next prev parent reply other threads:[~2026-02-17 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 17:42 [Rpm] CAKE-MQ merged to OpenWrt 25.12 today (February 15) Frantisek Borsik
2026-02-17 6:10 ` [Rpm] Re: [Cake] " dave seddon
2026-02-17 6:41 ` Stephen Hemminger [this message]
2026-02-17 13:23 ` [Rpm] Re: [Bloat] " Toke Høiland-Jørgensen
2026-02-17 14:34 ` [Rpm] Re: [Cake] Re: [Bloat] " Stephen Hemminger
2026-02-17 16:32 ` Toke Høiland-Jørgensen
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260216224131.5c5ae855@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dave.seddon.ca@gmail.com \
--cc=frantisek.borsik@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=ryan@rkhtech.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