From: Paolo Abeni <pabeni@redhat.com>
To: Kui-Feng Lee <thinker.li@gmail.com>,
dsahern@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, martin.lau@linux.dev,
kernel-team@meta.com, yhs@meta.com
Cc: Kui-Feng Lee <kuifeng@meta.com>
Subject: Re: [PATCH net-next v2 2/2] selftests: fib_tests: Add a test case for IPv6 garbage collection
Date: Thu, 20 Jul 2023 11:32:20 +0200 [thread overview]
Message-ID: <9743a6cc267276bfeba5b0fdcf7ba9a4077c67e1.camel@redhat.com> (raw)
In-Reply-To: <20230718180321.294721-3-kuifeng@meta.com>
On Tue, 2023-07-18 at 11:03 -0700, Kui-Feng Lee wrote:
> Add 10 IPv6 routes with expiration time. Wait for a few seconds
> to make sure they are removed correctly.
>
> Signed-off-by: Kui-Feng Lee <kuifeng@meta.com>
Same thing as the previous patch.
> ---
> tools/testing/selftests/net/fib_tests.sh | 49 +++++++++++++++++++++++-
> 1 file changed, 48 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/net/fib_tests.sh b/tools/testing/selftests/net/fib_tests.sh
> index 35d89dfa6f11..55bc6897513a 100755
> --- a/tools/testing/selftests/net/fib_tests.sh
> +++ b/tools/testing/selftests/net/fib_tests.sh
> @@ -9,7 +9,7 @@ ret=0
> ksft_skip=4
>
> # all tests in this script. Can be overridden with -t option
> -TESTS="unregister down carrier nexthop suppress ipv6_notify ipv4_notify ipv6_rt ipv4_rt ipv6_addr_metric ipv4_addr_metric ipv6_route_metrics ipv4_route_metrics ipv4_route_v6_gw rp_filter ipv4_del_addr ipv4_mangle ipv6_mangle ipv4_bcast_neigh"
> +TESTS="unregister down carrier nexthop suppress ipv6_notify ipv4_notify ipv6_rt ipv4_rt ipv6_addr_metric ipv4_addr_metric ipv6_route_metrics ipv4_route_metrics ipv4_route_v6_gw rp_filter ipv4_del_addr ipv4_mangle ipv6_mangle ipv4_bcast_neigh fib6_gc_test"
At this point is likely worthy splitting the above line in multiple
ones, something alike:
TESTS="unregister down carrier nexthop suppress ipv6_notify \
ipv4_notify ipv6_rt ipv4_rt ipv6_addr_metric ipv4_addr_metric
\
ipv6_route_metrics ipv4_route_metrics ipv4_route_v6_gw \
rp_filter ipv4_del_addr ipv4_mangle ipv6_mangle ipv4_bcast_neigh \
fib6_gc_test"
>
> VERBOSE=0
> PAUSE_ON_FAIL=no
> @@ -747,6 +747,52 @@ fib_notify_test()
> cleanup &> /dev/null
> }
>
> +fib6_gc_test()
> +{
> + setup
> +
> + echo
> + echo "Fib6 garbage collection test"
> + set -e
> +
> + OLD_INTERVAL=$(sysctl -n net.ipv6.route.gc_interval)
> + # Check expiration of routes every 3 seconds (GC)
> + $NS_EXEC sysctl -wq net.ipv6.route.gc_interval=3
> +
> + $IP link add dummy_10 type dummy
> + $IP link set dev dummy_10 up
> + $IP -6 address add 2001:10::1/64 dev dummy_10
> +
> + for i in 0 1 2 3 4 5 6 7 8 9; do
$(seq 0 9)
> + # Expire route after 2 seconds
> + $IP -6 route add 2001:20::1$i \
> + via 2001:10::2 dev dummy_10 expires 2
> + done
> + N_EXP=$($IP -6 route list |grep expires|wc -l)
> + if [ $N_EXP -ne 10 ]; then
> + echo "FAIL: expected 10 routes with expires, got $N_EXP"
> + ret=1
> + else
> + sleep 4
> + N_EXP_s20=$($IP -6 route list |grep expires|wc -l)
> +
> + if [ $N_EXP_s20 -ne 0 ]; then
> + echo "FAIL: expected 0 routes with expires, got $N_EXP_s20"
> + ret=1
> + else
> + ret=0
> + fi
> + fi
Possibly also worth trying with a few K of permanent routes, and dump
the time required in both cases?
> +
> + set +e
> +
> + log_test $ret 0 "ipv6 route garbage collection"
> +
> + sysctl -wq net.ipv6.route.gc_interval=$OLD_INTERVAL
No need to restore, gc_interval is a per namespace param specific
>
next prev parent reply other threads:[~2023-07-20 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 18:03 [PATCH net-next v2 0/2] Remove expired routes with a Kui-Feng Lee
2023-07-18 18:03 ` [PATCH net-next v2 1/2] net/ipv6: Remove expired routes with a separated list of routes Kui-Feng Lee
2023-07-20 9:18 ` Paolo Abeni
2023-07-20 16:31 ` Kui-Feng Lee
2023-07-18 18:03 ` [PATCH net-next v2 2/2] selftests: fib_tests: Add a test case for IPv6 garbage collection Kui-Feng Lee
2023-07-20 9:32 ` Paolo Abeni [this message]
2023-07-20 16:32 ` Kui-Feng Lee
2023-07-20 21:36 ` Kui-Feng Lee
2023-07-21 7:14 ` Paolo Abeni
2023-07-21 18:31 ` Kui-Feng Lee
2023-07-21 20:01 ` David Ahern
2023-07-21 20:57 ` Kui-Feng Lee
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=9743a6cc267276bfeba5b0fdcf7ba9a4077c67e1.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=thinker.li@gmail.com \
--cc=yhs@meta.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;
as well as URLs for NNTP newsgroup(s).