From: David Ahern <dsahern@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, horms@kernel.org, willemb@google.com
Subject: Re: [PATCH net-next v3 1/3] ipv6: Select best matching nexthop object in fib6_table_lookup()
Date: Thu, 11 Jun 2026 12:25:15 -0600 [thread overview]
Message-ID: <ee1f0858-5976-48fa-9101-41f036b9166e@kernel.org> (raw)
In-Reply-To: <20260611154605.992528-2-idosch@nvidia.com>
On 6/11/26 9:46 AM, Ido Schimmel wrote:
> Currently, when using multipath routes without nexthop objects,
> fib6_table_lookup() selects the nexthop with the highest score. This
> means that when both a source address and an oif are specified, the
> nexthop that is chosen is the one that matches in terms of oif:
>
> # sysctl -wq net.ipv6.conf.all.forwarding=1
> # ip address add 2001:db8:2::1/64 dev lo
> # ip route add 2001:db8:10::/64 nexthop via fe80::1 dev dummy1 nexthop via fe80::2 dev dummy2
>
> # perf record -e fib6:fib6_table_lookup -- bash -c "for i in {1..100}; do ip route get 2001:db8:10::${i} from 2001:db8:2::1 oif dummy1; done > /dev/null"
> # perf script | grep -o dummy[0-9] | sort | uniq -c
> 100 dummy1
> # perf record -e fib6:fib6_table_lookup -- bash -c "for i in {1..100}; do ip route get 2001:db8:10::${i} from 2001:db8:2::1 oif dummy2; done > /dev/null"
> # perf script | grep -o dummy[0-9] | sort | uniq -c
> 100 dummy2
>
> When using nexthop objects, fib6_table_lookup() selects the first
> matching nexthop and not necessarily the one with the highest score:
>
> # ip nexthop add id 1 via fe80::1 dev dummy1
> # ip nexthop add id 2 via fe80::2 dev dummy2
> # ip nexthop add id 3 group 1/2
> # ip route add 2001:db8:20::/64 nhid 3
>
> # perf record -e fib6:fib6_table_lookup -- bash -c "for i in {1..100}; do ip route get 2001:db8:20::${i} from 2001:db8:2::1 oif dummy1; done > /dev/null"
> # perf script | grep -o dummy[0-9] | sort | uniq -c
> 100 dummy1
> # perf record -e fib6:fib6_table_lookup -- bash -c "for i in {1..100}; do ip route get 2001:db8:20::${i} from 2001:db8:2::1 oif dummy2; done > /dev/null"
> # perf script | grep -o dummy[0-9] | sort | uniq -c
> 100 dummy1
>
> This is not very significant right now because the nexthop is later
> overwritten during path selection in fib6_select_path(). However, the
> next patch is going to skip path selection when we have an oif match
> during output route lookup.
>
> As a preparation for this change, align the nexthop object behavior with
> the legacy one and make sure that fib6_table_lookup() always selects the
> best matching nexthop. Do that by always returning 0 from
> rt6_nh_find_match() in order not to terminate the loop in
> nexthop_for_each_fib6_nh() and storing in arg->nh the best matching
> nexthop so far.
>
> Behavior after the change:
>
> # perf record -e fib6:fib6_table_lookup -- bash -c "for i in {1..100}; do ip route get 2001:db8:20::${i} from 2001:db8:2::1 oif dummy1; done > /dev/null"
> # perf script | grep -o dummy[0-9] | sort | uniq -c
> 100 dummy1
> # perf record -e fib6:fib6_table_lookup -- bash -c "for i in {1..100}; do ip route get 2001:db8:20::${i} from 2001:db8:2::1 oif dummy2; done > /dev/null"
> # perf script | grep -o dummy[0-9] | sort | uniq -c
> 100 dummy2
>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
> net/ipv6/route.c | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2026-06-11 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 15:46 [PATCH net-next v3 0/3] ipv6: Honor oif when choosing nexthop for locally generated traffic Ido Schimmel
2026-06-11 15:46 ` [PATCH net-next v3 1/3] ipv6: Select best matching nexthop object in fib6_table_lookup() Ido Schimmel
2026-06-11 18:25 ` David Ahern [this message]
2026-06-11 15:46 ` [PATCH net-next v3 2/3] ipv6: Honor oif when choosing nexthop for locally generated traffic Ido Schimmel
2026-06-11 15:46 ` [PATCH net-next v3 3/3] selftests: fib_tests: Add test cases for route lookup with oif Ido Schimmel
2026-06-11 18:28 ` David Ahern
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=ee1f0858-5976-48fa-9101-41f036b9166e@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
/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