Netdev List
 help / color / mirror / Atom feed
From: Antoine Tenart <atenart@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
	steffen.klassert@secunet.com, willemdebruijn.kernel@gmail.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH net v3 0/4] gro: various fixes related to UDP tunnels
Date: Mon, 25 Mar 2024 11:16:24 +0100	[thread overview]
Message-ID: <171136178469.5526.13954285367211651380@kwain> (raw)
In-Reply-To: <20240322155550.3779c85a@kernel.org>

Quoting Jakub Kicinski (2024-03-22 23:55:50)
> On Fri, 22 Mar 2024 12:46:19 +0100 Antoine Tenart wrote:
> > We found issues when a UDP tunnel endpoint is in a different netns than
> > where UDP GRO happens. This kind of setup is actually quite diverse,
> > from having one leg of the tunnel on a remove host, to having a tunnel
> > between netns (eg. being bridged in another one or on the host). In our
> > case that UDP tunnel was geneve.
> 
> I think this series makes net/udpgro_fwd.sh selftest fail.

Thanks! Sorry for not checking this earlier...

What happens is the vxlan tunnel tests expect GRO to happen at the veth
level which is exactly the issues this series is fixing.

The below diff should fix the tests. I think it's good to keep them to
ensure GRO is actually not happening while packets are in an UDP tunnel;
I also removed the "UDP tunnel fwd perf" test as it's not providing any
useful data now IMO.

diff --git a/tools/testing/selftests/net/udpgro_fwd.sh b/tools/testing/selftests/net/udpgro_fwd.sh
index 380cb15e942e..83ed987cff34 100755
--- a/tools/testing/selftests/net/udpgro_fwd.sh
+++ b/tools/testing/selftests/net/udpgro_fwd.sh
@@ -244,7 +244,7 @@ for family in 4 6; do
        create_vxlan_pair
        ip netns exec $NS_DST ethtool -K veth$DST generic-receive-offload on
        ip netns exec $NS_DST ethtool -K veth$DST rx-gro-list on
-       run_test "GRO frag list over UDP tunnel" $OL_NET$DST 1 1
+       run_test "GRO frag list over UDP tunnel" $OL_NET$DST 10 10
        cleanup
 
        # use NAT to circumvent GRO FWD check
@@ -258,13 +258,7 @@ for family in 4 6; do
        # load arp cache before running the test to reduce the amount of
        # stray traffic on top of the UDP tunnel
        ip netns exec $NS_SRC $PING -q -c 1 $OL_NET$DST_NAT >/dev/null
-       run_test "GRO fwd over UDP tunnel" $OL_NET$DST_NAT 1 1 $OL_NET$DST
-       cleanup
-
-       create_vxlan_pair
-       run_bench "UDP tunnel fwd perf" $OL_NET$DST
-       ip netns exec $NS_DST ethtool -K veth$DST rx-udp-gro-forwarding on
-       run_bench "UDP tunnel GRO fwd perf" $OL_NET$DST
+       run_test "GRO fwd over UDP tunnel" $OL_NET$DST_NAT 10 10 $OL_NET$DST
        cleanup
 done

      reply	other threads:[~2024-03-25 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 11:46 [PATCH net v3 0/4] gro: various fixes related to UDP tunnels Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 1/4] udp: do not accept non-tunnel GSO skbs landing in a tunnel Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 2/4] gro: fix ownership transfer Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 3/4] udp: do not transition UDP GRO fraglist partial checksums to unnecessary Antoine Tenart
2024-03-22 17:29   ` Willem de Bruijn
2024-03-25 10:37     ` Antoine Tenart
2024-03-25 18:39       ` Willem de Bruijn
2024-03-26  9:44         ` Antoine Tenart
2024-03-26 13:37           ` Willem de Bruijn
2024-03-22 11:46 ` [PATCH net v3 4/4] udp: prevent local UDP tunnel packets from being GROed Antoine Tenart
2024-03-22 22:55 ` [PATCH net v3 0/4] gro: various fixes related to UDP tunnels Jakub Kicinski
2024-03-25 10:16   ` Antoine Tenart [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=171136178469.5526.13954285367211651380@kwain \
    --to=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox