From: pgnd <pgnd@dev-mail.net>
To: netfilter@vger.kernel.org
Subject: correct nft v1.1.0 usage for flowtable h/w offload? `flags offload` &/or `devices=`
Date: Sun, 11 Aug 2024 10:43:35 -0400 [thread overview]
Message-ID: <890f23df-cdd6-4dab-9979-d5700d8b914b@dev-mail.net> (raw)
i'm setting up nftables flowtable for h/w offload, per
https://wiki.nftables.org/wiki-nftables/index.php/Flowtables
https://docs.kernel.org/networking/nf_flowtable.html#hardware-offload
https://thermalcircle.de/doku.php?id=blog:linux:flowtables_1_a_netfilter_nftables_fastpath
&
a slew of older posts @ ML ...
on
/usr/local/sbin/nft -V
nftables v1.1.0 (Commodore Bullmoose)
cli: editline
json: yes
minigmp: no
libxtables: no
uname -rm
6.10.3-200.fc40.x86_64 x86_64
with
lspci | grep -i eth
02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
03:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
ethtool -k enp3s0 | grep -i offload.*on
tcp-segmentation-offload: on
generic-segmentation-offload: on
generic-receive-offload: on
rx-vlan-offload: on
tx-vlan-offload: on
hw-tc-offload: on
(which, iiuc, is sufficient?)
a test config
cat test.nft
#!/usr/local/sbin/nft -f
table inet filter {
flowtable f {
hook ingress priority 0;
devices = { enp2s0, enp3s0 };
}
chain input {
type filter hook input priority 0;
policy accept;
}
chain forward {
type filter hook forward priority 1;
policy drop;
ct state invalid drop;
tcp dport { 80, 443 } ct state established flow offload @f;
ct state { established, related } accept;
accept;
}
}
fails conf check,
nft -c -f ./test.nft
./test.nft:8:12-12: Error: Could not process rule: Operation not supported
flowtable f {
^
otoh, per example @
https://docs.kernel.org/networking/nf_flowtable.html#hardware-offload
edit
flowtable f {
hook ingress priority 0;
- devices = { enp2s0, enp3s0 };
+ flags offload;
}
passes conf check. and after load
nft list flowtables
table inet filter {
flowtable f {
hook ingress priority filter
flags offload
}
}
what's the correct/current usage for flowtable declaration in hardware offload use case?
as documented @ wiki, or kernel docs?
_seems_ it's kernel docs ...
reading @,
https://netfilter.org/projects/nftables/files/changes-nftables-1.1.0.txt
i don't find (yet) the change re `flags offload` usage.
what commit introduced it?
reply other threads:[~2024-08-11 14:43 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=890f23df-cdd6-4dab-9979-d5700d8b914b@dev-mail.net \
--to=pgnd@dev-mail.net \
--cc=netfilter@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).