From: Petr Machata <petrm@nvidia.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
"Simon Horman" <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
Shuah Khan <shuah@kernel.org>,
"Willem de Bruijn" <willemdebruijn.kernel@gmail.com>,
<sdf@fomichev.me>, <petrm@nvidia.com>, <razor@blackwall.org>,
<idosch@nvidia.com>
Subject: Re: [PATCH v3 net-next 10/10] selftests: net: tests for add double tunneling GRO/GSO
Date: Thu, 15 Jan 2026 11:13:30 +0100 [thread overview]
Message-ID: <871pjr6t08.fsf@nvidia.com> (raw)
In-Reply-To: <551e2839d870351c34f656530bfd5865b9b131bc.1768410519.git.pabeni@redhat.com>
Paolo Abeni <pabeni@redhat.com> writes:
> Create a simple, netns-based topology with double, nested UDP tunnels and
> perform TSO transfers on top.
>
> Explicitly enable GSO and/or GRO and check the skb layout consistency with
> different configuration allowing (or not) GSO frames to be delivered on
> the other end.
>
> The trickest part is account in a robust way the aggregated/unaggregated
> packets with double encapsulation: use a classic bpf filter for it.
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Looks OK overall, just:
> diff --git a/tools/testing/selftests/net/double_udp_encap.sh b/tools/testing/selftests/net/double_udp_encap.sh
> new file mode 100755
> index 000000000000..055f65b4d18d
> --- /dev/null
> +++ b/tools/testing/selftests/net/double_udp_encap.sh
> +# tcp retransmisions will break the accounting
> +[ "$KSFT_MACHINE_SLOW" = yes ] && FAIL_TO_XFAIL=yes
You should just be able to call `xfail_on_slow' without an argument to
apply the setting globally.
Selftests shouldn't have to touch FAIL_TO_XFAIL directly.
prev parent reply other threads:[~2026-01-15 11:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 17:20 [PATCH v3 net-next 00/10] geneve: introduce double tunnel GSO/GRO support Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 01/10] net: introduce mangleid_features Paolo Abeni
2026-01-14 18:07 ` Eric Dumazet
2026-01-19 10:13 ` Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 02/10] geneve: expose gso partial features for tunnel offload Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 03/10] vxlan: " Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 04/10] geneve: add netlink support for GRO hint Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 05/10] geneve: constify geneve_hlen() Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 06/10] geneve: pass the geneve device ptr to geneve_build_skb() Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 07/10] geneve: add GRO hint output path Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 08/10] geneve: extract hint option at GRO stage Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 09/10] geneve: use GRO hint option in the RX path Paolo Abeni
2026-01-14 17:20 ` [PATCH v3 net-next 10/10] selftests: net: tests for add double tunneling GRO/GSO Paolo Abeni
2026-01-15 10:13 ` Petr Machata [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=871pjr6t08.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--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=razor@blackwall.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=willemdebruijn.kernel@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 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.