From: "Eva Kurchatova (Virtuozzo)" <eva.kurchatova@virtuozzo.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Alexander Lobakin <alobakin@pm.me>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] udp: let rx-udp-gro-forwarding aggregate under encapsulation
Date: Sun, 18 Oct 2026 19:54:30 +0300 [thread overview]
Message-ID: <dc9eda55-2688-40f7-9b0a-7dfa0e5cbf3d@virtuozzo.com> (raw)
In-Reply-To: <willemdebruijn.kernel.2f0d78527930f@gmail.com>
On Wed, 15 Oct 2026 02:56, Willem de Bruijn wrote:
> Uses encapsulation in the same network namespace as where the test
> runs? If different namespaces, the socket lookup should fail and
> thus the behavior be the same as on a host without a tunnel.
Different one: the vxlan sat in the init namespace, the test in the
ns it creates. The static key is global, though, so the tunnel turns
the lookup on everywhere, and the lookup then runs in the test's
receiving namespace, where it finds the test's own receiver: a plain
socket bound to any address, without UDP_GRO. That is why the check
goes from 1 to 10 the moment a tunnel exists anywhere on the host.
prev parent reply other threads:[~2026-10-18 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 16:38 Eva Kurchatova
2026-10-12 10:40 ` netdev-bot+sashiko
2026-10-15 2:56 ` Willem de Bruijn
2026-10-18 16:54 ` Eva Kurchatova (Virtuozzo) [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=dc9eda55-2688-40f7-9b0a-7dfa0e5cbf3d@virtuozzo.com \
--to=eva.kurchatova@virtuozzo.com \
--cc=alobakin@pm.me \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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
all inboxes | Powered by JetHome®