From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Simon Horman <horms@kernel.org>,
David Ahern <dsahern@kernel.org>,
kuniyu@amazon.com
Subject: Re: [PATCH v3 net-next 1/2] udp_tunnel: create a fastpath GRO lookup.
Date: Tue, 11 Mar 2025 13:55:06 -0400 [thread overview]
Message-ID: <67d078fa5b11e_2fc2f8294ed@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <44a45278-8ebf-4d79-b64d-f1ad557c8948@redhat.com>
Paolo Abeni wrote:
> On 3/11/25 6:29 PM, Willem de Bruijn wrote:
> > Paolo Abeni wrote:
> >> On 3/11/25 3:32 AM, Willem de Bruijn wrote:
> >>> What about packets with a non-local daddr (e.g., forwarding)?
> >>
> >> I'm unsure if I understand the question. Such incoming packets at the
> >> GRO stage will match the given tunnel socket, either by full socket
> >> lookup or by dport only selection.
> >>
> >> If the GSO packet will be forwarded, it will segmented an xmit time.
> >>
> >> Possibly you mean something entirely different?!?
> >
> > Thanks, no that is exactly what I meant:
> >
> > Is a false positive possible? So answer is yes.
> >
> > Is it safe. So, yes again, as further down the stack it just handles
> > the GSO packet correctly.
> >
> > Would you mind adding that to commit message explicitly, since you're
> > respinning anyway?
>
> I was confused because this patch does not change the current behaviour.
Oh right, this is also true of the existing __udp6_lib_lookup path.
> I'll add a note in v4.
Thanks
next prev parent reply other threads:[~2025-03-11 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 19:09 [PATCH v3 net-next 0/2] udp_tunnel: GRO optimizations Paolo Abeni
2025-03-10 19:09 ` [PATCH v3 net-next 1/2] udp_tunnel: create a fastpath GRO lookup Paolo Abeni
2025-03-11 2:32 ` Willem de Bruijn
2025-03-11 16:38 ` Paolo Abeni
2025-03-11 17:29 ` Willem de Bruijn
2025-03-11 17:37 ` Paolo Abeni
2025-03-11 17:55 ` Willem de Bruijn [this message]
2025-03-10 19:09 ` [PATCH v3 net-next 2/2] udp_tunnel: use static call for GRO hooks when possible Paolo Abeni
2025-03-11 2:51 ` Willem de Bruijn
2025-03-11 17:24 ` Paolo Abeni
2025-03-11 17:30 ` Willem de Bruijn
2025-03-11 5:49 ` Kuniyuki Iwashima
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=67d078fa5b11e_2fc2f8294ed@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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