From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nf-next v2 0/3] ipv6: switch nft_fib_ipv6 to fib6_lookup
Date: Thu, 26 Feb 2026 21:21:23 +0100 [thread overview]
Message-ID: <20260226202129.15033-1-fw@strlen.de> (raw)
Existing code works but it requires a temporary dst object that is
released again right away.
Switch to fib6_lookup + RT6_LOOKUP_F_DST_NOREF: no need for temporary dst
objects and refcount overhead anymore.
Provides ~13% improvement in match performance.
First two patches are preparations:
We need to export fib6_lookup, only alternative would be an indirection
via the ipv6 stub, but thats expensive.
Also, nft_fib_ipv6 uses a helper that requires a ipv6 dst, but we no
longer have that. Split this and let the new helper work without the
dst object.
Changes since v1:
- fix compiler error without ipv6 multi-table support
- split ipv6_anycast_destination, use the new helper
Florian Westphal (3):
ipv6: export fib6_lookup for nft_fib_ipv6
ipv6: make ipv6_anycast_destination logic useable without dst_entry
netfilter: nft_fib_ipv6: switch to fib6_lookup
include/net/ip6_route.h | 15 ++++--
net/ipv6/fib6_rules.c | 3 ++
net/ipv6/ip6_fib.c | 3 ++
net/ipv6/netfilter/nft_fib_ipv6.c | 79 +++++++++++++++++++------------
4 files changed, 66 insertions(+), 34 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-26 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 20:21 Florian Westphal [this message]
2026-02-26 20:21 ` [PATCH nf-next v2 1/3] ipv6: export fib6_lookup for nft_fib_ipv6 Florian Westphal
2026-02-26 20:21 ` [PATCH nf-next v2 2/3] ipv6: make ipv6_anycast_destination logic useable without dst_entry Florian Westphal
2026-02-26 20:21 ` [PATCH nf-next v2 3/3] netfilter: nft_fib_ipv6: switch to fib6_lookup Florian Westphal
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=20260226202129.15033-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@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