From: Julius Bairaktaris <julius@bairaktaris.de>
To: bloat@lists.bufferbloat.net
Cc: cake@lists.bufferbloat.net, libreqos@lists.bufferbloat.net
Subject: [Bloat] Making nftables flowtable offload (SW & HW) preserve skb->priority for SQM/CAKE
Date: Wed, 14 Oct 2026 09:36:39 +0000 [thread overview]
Message-ID: <CAC1t37LyJaAabyy3eZo6jZt2pwPL5Ey293qui3s6-VCSfGsN3g@mail.gmail.com> (raw)
Hi everyone,
I have a patch series on netfilter-devel that fixes a long-standing
issue where nftables flowtable offloading breaks packet prioritization,
and it just got reviewed and tested by NVIDIA on ConnectX-7:
https://lore.kernel.org/netfilter-devel/20261004171636.3545085-1-julius@bairaktaris.de/
Right now, as soon as a connection enters a flowtable (`flow add`),
nf_flow_table drops skb->priority. That means `meta priority set` (or
IPv4 TOS-derived priority) only works for the first few slow-path
packets, after which offloaded flows lose their priority and land in the
wrong qdisc tin/band.
This series fixes that by saving skb->priority in the flowtable entry so
packets on the software fastpath keep their priority for CAKE/fq_codel,
and by emitting FLOW_ACTION_PRIORITY to hardware offload drivers
(wired up for MediaTek/Airoha PPE, plus the mlx5e handler NVIDIA just
verified so ConnectX NICs keep flows offloaded in hardware).
Thought this might be useful for anyone here running nftables flowtables
alongside SQM/QoS. Testing and feedback are very welcome!
Best,
Julius
reply other threads:[~2026-10-14 9:37 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
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=CAC1t37LyJaAabyy3eZo6jZt2pwPL5Ey293qui3s6-VCSfGsN3g@mail.gmail.com \
--to=julius@bairaktaris.de \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=libreqos@lists.bufferbloat.net \
/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