From: Kui-Feng Lee <sinquersw@gmail.com>
To: Kui-Feng Lee <thinker.li@gmail.com>,
netdev@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
kernel-team@meta.com, kuba@kernel.org, davem@davemloft.net,
dsahern@kernel.org
Cc: kuifeng@meta.com
Subject: Re: [PATCH bpf-next] selftests/net: force synchronized GC for a test.
Date: Fri, 23 Feb 2024 00:10:16 -0800 [thread overview]
Message-ID: <1c1e30f4-c898-4fa7-8f26-9eee1b1f0f09@gmail.com> (raw)
In-Reply-To: <20240223075251.2039008-1-thinker.li@gmail.com>
Sorry! Post the patch to a wrong list.
On 2/22/24 23:52, Kui-Feng Lee wrote:
> Due to the slowness of the test environment, always set off a synchronized
> GC after waiting for GC. This can fix the problem that Fib6 garbage
> collection test fails occasionally.
>
> Signed-off-by: Kui-Feng Lee <thinker.li@gmail.com>
> ---
> tools/testing/selftests/net/fib_tests.sh | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/net/fib_tests.sh b/tools/testing/selftests/net/fib_tests.sh
> index 3ec1050e47a2..0a82c9bc07bb 100755
> --- a/tools/testing/selftests/net/fib_tests.sh
> +++ b/tools/testing/selftests/net/fib_tests.sh
> @@ -823,7 +823,9 @@ fib6_gc_test()
> $IP -6 route add 2001:20::$i \
> via 2001:10::2 dev dummy_10 expires $EXPIRE
> done
> + # Wait for GC
> sleep $(($EXPIRE * 2 + 1))
> + $NS_EXEC sysctl -wq net.ipv6.route.flush=1
> check_rt_num 0 $($IP -6 route list |grep expires|wc -l)
> log_test $ret 0 "ipv6 route garbage collection (with permanent routes)"
>
> @@ -864,7 +866,7 @@ fib6_gc_test()
>
> # Wait for GC
> sleep $(($EXPIRE * 2 + 1))
> -
> + $NS_EXEC sysctl -wq net.ipv6.route.flush=1
> check_rt_num 5 $($IP -6 route list |grep -v expires|grep 2001:20::|wc -l)
> log_test $ret 0 "ipv6 route garbage collection (replace with permanent)"
>
prev parent reply other threads:[~2024-02-23 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 7:52 [PATCH bpf-next] selftests/net: force synchronized GC for a test Kui-Feng Lee
2024-02-23 8:10 ` Kui-Feng Lee [this message]
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=1c1e30f4-c898-4fa7-8f26-9eee1b1f0f09@gmail.com \
--to=sinquersw@gmail.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--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 \
/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