From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>, Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org,
Vadim Fedorenko <vadim.fedorenko@linux.dev>
Subject: Re: [PATCH net v2 2/2] selftests: fib_test: Add test case for ipv4 multi nexthops
Date: Sun, 21 Dec 2025 10:59:18 -0500 [thread overview]
Message-ID: <willemdebruijn.kernel.14a486c1824f2@gmail.com> (raw)
In-Reply-To: <20251220032335.3517241-2-vadim.fedorenko@linux.dev>
Vadim Fedorenko wrote:
> The test checks that with multi nexthops route the preferred route is the
> one which matches source ip. In case when source ip is on dummy
> interface, it checks that the routes are balanced.
>
> Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Reviewed-by: Willem de Bruijn <willemb@google.com>
> ---
> v1 -> v2:
> - move tests to fib_tests.sh
> ---
> tools/testing/selftests/net/fib_tests.sh | 70 +++++++++++++++++++++++-
> 1 file changed, 69 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/net/fib_tests.sh b/tools/testing/selftests/net/fib_tests.sh
> index a88f797c549a..c5694cc4ddd2 100755
> --- a/tools/testing/selftests/net/fib_tests.sh
> +++ b/tools/testing/selftests/net/fib_tests.sh
> @@ -12,7 +12,7 @@ TESTS="unregister down carrier nexthop suppress ipv6_notify ipv4_notify \
> ipv4_route_metrics ipv4_route_v6_gw rp_filter ipv4_del_addr \
> ipv6_del_addr ipv4_mangle ipv6_mangle ipv4_bcast_neigh fib6_gc_test \
> ipv4_mpath_list ipv6_mpath_list ipv4_mpath_balance ipv6_mpath_balance \
> - fib6_ra_to_static"
> + ipv4_mpath_balance_preferred fib6_ra_to_static"
>
> VERBOSE=0
> PAUSE_ON_FAIL=no
> @@ -2751,6 +2751,73 @@ ipv4_mpath_balance_test()
> forwarding_cleanup
> }
>
> +get_route_dev_src()
> +{
> + local pfx="$1"
> + local src="$2"
only with my highly pedantic hat on, and only if respinning: these can be local -r
> + local out
> +
> + if out=$($IP -j route get "$pfx" from "$src" | jq -re ".[0].dev"); then
> + echo "$out"
> + fi
> +}
> +
> +ipv4_mpath_preferred()
> +{
> + local src_ip=$1
> + local pref_dev=$2
> + local dev routes
> + local route0=0
> + local route1=0
> + local pref_route=0
> + num_routes=254
> +
> + for i in $(seq 1 $num_routes) ; do
> + dev=$(get_route_dev_src 172.16.105.$i $src_ip)
Similarly, I was going to ask to avoid open coding the ip prefixes
repeatedly. But that is the style in this file, so fine to follow.
> + if [ "$dev" = "$pref_dev" ]; then
> + pref_route=$((pref_route+1))
> + elif [ "$dev" = "veth1" ]; then
> + route0=$((route0+1))
> + elif [ "$dev" = "veth3" ]; then
> + route1=$((route1+1))
> + fi
> + done
> +
> + routes=$((route0+route1))
> +
> + [ "$VERBOSE" = "1" ] && echo "multipath: routes seen: ($route0,$route1,$pref_route)"
> +
> + if [ x"$pref_dev" = x"" ]; then
> + [[ $routes -ge $num_routes ]] && [[ $route0 -gt 0 ]] && [[ $route1 -gt 0 ]]
> + else
> + [[ $pref_route -ge $num_routes ]]
> + fi
> +
> +}
> +
> +ipv4_mpath_balance_preferred_test()
> +{
> + echo
> + echo "IPv4 multipath load balance preferred route"
> +
> + forwarding_setup
> +
> + $IP route add 172.16.105.0/24 \
> + nexthop via 172.16.101.2 \
> + nexthop via 172.16.103.2
> +
> + ipv4_mpath_preferred 172.16.101.1 veth1
> + log_test $? 0 "IPv4 multipath loadbalance from veth1"
> +
> + ipv4_mpath_preferred 172.16.103.1 veth3
> + log_test $? 0 "IPv4 multipath loadbalance from veth3"
> +
> + ipv4_mpath_preferred 198.51.100.1
> + log_test $? 0 "IPv4 multipath loadbalance from dummy"
> +
> + forwarding_cleanup
> +}
> +
> ipv6_mpath_balance_test()
> {
> echo
> @@ -2861,6 +2928,7 @@ do
> ipv6_mpath_list) ipv6_mpath_list_test;;
> ipv4_mpath_balance) ipv4_mpath_balance_test;;
> ipv6_mpath_balance) ipv6_mpath_balance_test;;
> + ipv4_mpath_balance_preferred) ipv4_mpath_balance_preferred_test;;
> fib6_ra_to_static) fib6_ra_to_static;;
>
> help) echo "Test names: $TESTS"; exit 0;;
> --
> 2.47.3
>
next prev parent reply other threads:[~2025-12-21 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 3:23 [PATCH net v2 1/2] net: fib: restore ECMP balance from loopback Vadim Fedorenko
2025-12-20 3:23 ` [PATCH net v2 2/2] selftests: fib_test: Add test case for ipv4 multi nexthops Vadim Fedorenko
2025-12-21 15:59 ` Willem de Bruijn [this message]
2025-12-21 15:55 ` [PATCH net v2 1/2] net: fib: restore ECMP balance from loopback Willem de Bruijn
2025-12-21 16:58 ` Ido Schimmel
2025-12-21 18:49 ` Vadim Fedorenko
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=willemdebruijn.kernel.14a486c1824f2@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--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=shuah@kernel.org \
--cc=vadim.fedorenko@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.