From: Alice Mikityanska <alice.kernel@fastmail.im>
To: Matthieu Baerts <matttbe@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
Alice Mikityanska <alice@isovalent.com>
Subject: [PATCH net-next 3/4] selftests: net: Lower threshold with csum offload off in big_tcp_tunnels.sh
Date: Fri, 14 Aug 2026 22:41:23 +0300 [thread overview]
Message-ID: <20260814194124.3102581-4-alice.kernel@fastmail.im> (raw)
In-Reply-To: <20260814194124.3102581-1-alice.kernel@fastmail.im>
From: Alice Mikityanska <alice@isovalent.com>
With checksum offload disabled, much fewer BIG TCP packets are generated
due to overall loss of throughput. Use a separate threshold in these
tests, which is 1/10 of the threshold set for the rest of tests.
Signed-off-by: Alice Mikityanska <alice@isovalent.com>
---
tools/testing/selftests/net/big_tcp_tunnels.sh | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/net/big_tcp_tunnels.sh b/tools/testing/selftests/net/big_tcp_tunnels.sh
index e27774eae20e..1f1c811c563c 100755
--- a/tools/testing/selftests/net/big_tcp_tunnels.sh
+++ b/tools/testing/selftests/net/big_tcp_tunnels.sh
@@ -114,6 +114,8 @@ cleanup() {
}
do_test() {
+ local packets_threshold="$PACKETS_THRESHOLD"
+
# When tx csum offload is off, software GSO is performed before passing the
# packet to veth. Check BIG TCP packets inside the VXLAN tunnel to verify
# the software checksum path: if the checksum code is broken, these packets
@@ -132,6 +134,7 @@ do_test() {
else
IPTABLES=ip6tables
fi
+ packets_threshold=$(( PACKETS_THRESHOLD / 10 ))
fi
if [ "$2" = 4 ]; then
IPTABLES_SACK=iptables
@@ -164,8 +167,8 @@ do_test() {
echo "Captured BIG TCP RX packets: $PACKETS_SERVER"
echo "Captured BIG TCP TX packets: $PACKETS_CLIENT"
echo "Captured TCP SACK packets: $PACKETS_SACK"
- [ "$PACKETS_SERVER" -gt "$PACKETS_THRESHOLD" ] || return 1
- [ "$PACKETS_CLIENT" -gt "$PACKETS_THRESHOLD" ] || return 1
+ [ "$PACKETS_SERVER" -gt "$packets_threshold" ] || return 1
+ [ "$PACKETS_CLIENT" -gt "$packets_threshold" ] || return 1
[ "$PACKETS_SACK" -lt "$(( PACKETS_CLIENT / 2 ))" ] || return 1
}
--
2.55.0
next prev parent reply other threads:[~2026-08-14 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 19:41 [PATCH net-next 0/4] Improve stability of big_tcp_tunnels.sh selftest Alice Mikityanska
2026-08-14 19:41 ` [PATCH net-next 1/4] selftests: net: Wait for netserver to launch Alice Mikityanska
2026-08-14 19:41 ` [PATCH net-next 2/4] selftests: net: Lower threshold on debug kernels for big_tcp_tunnels.sh Alice Mikityanska
2026-08-14 23:07 ` Matthieu Baerts
2026-08-19 17:20 ` Alice Mikityanska
2026-08-14 19:41 ` Alice Mikityanska [this message]
2026-08-14 19:41 ` [PATCH net-next 4/4] selftests: net: Fix slow configurations in big_tcp_tunnels.sh Alice Mikityanska
2026-08-19 9:25 ` Matthieu Baerts
2026-08-19 17:21 ` Alice Mikityanska
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=20260814194124.3102581-4-alice.kernel@fastmail.im \
--to=alice.kernel@fastmail.im \
--cc=alice@isovalent.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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 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.