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>
Subject: Re: [PATCH v2 net-next 2/2] udp_tunnel: use static call for GRO hooks when possible
Date: Sun, 09 Mar 2025 23:30:41 -0400 [thread overview]
Message-ID: <67ce5ce1722a4_20941f294a0@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <2dfd7292-901c-4155-9c80-954d2b0c7507@redhat.com>
Paolo Abeni wrote:
> On 3/8/25 7:40 PM, Willem de Bruijn wrote:
> > Paolo Abeni wrote:
> >> diff --git a/net/ipv4/udp_offload.c b/net/ipv4/udp_offload.c
> >> index 054d4d4a8927f..f06dd82d28562 100644
> >> --- a/net/ipv4/udp_offload.c
> >> +++ b/net/ipv4/udp_offload.c
> >> @@ -15,6 +15,39 @@
> >> #include <net/udp_tunnel.h>
> >>
> >> #if IS_ENABLED(CONFIG_NET_UDP_TUNNEL)
> >> +
> >> +/*
> >> + * Dummy GRO tunnel callback; should never be invoked, exists
> >> + * mainly to avoid dangling/NULL values for the udp tunnel
> >> + * static call.
> >> + */
> >> +static struct sk_buff *dummy_gro_rcv(struct sock *sk,
> >> + struct list_head *head,
> >> + struct sk_buff *skb)
> >> +{
> >> + WARN_ON_ONCE(1);
> >> + NAPI_GRO_CB(skb)->flush = 1;
> >> + return NULL;
> >> +}
> >> +
> >> +typedef struct sk_buff *(*udp_tunnel_gro_rcv_t)(struct sock *sk,
> >> + struct list_head *head,
> >> + struct sk_buff *skb);
> >> +
> >> +struct udp_tunnel_type_entry {
> >> + udp_tunnel_gro_rcv_t gro_receive;
> >> + refcount_t count;
> >> +};
> >> +
> >> +#define UDP_MAX_TUNNEL_TYPES (IS_ENABLED(CONFIG_GENEVE) + \
> >> + IS_ENABLED(CONFIG_VXLAN) * 2 + \
> >> + IS_ENABLED(CONFIG_FOE) * 2)
> >
> > CONFIG_BAREUDP
>
> Why? AFAICS BAREUDP does not implement the gro_receive callback. UDP
> tunnel without such callback are irrelevant here.
You're right, of course. I looked at the wrong callback. Sorry.
prev parent reply other threads:[~2025-03-10 3:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 18:13 [PATCH v2 net-next 0/2] udp_tunnel: GRO optimizations Paolo Abeni
2025-03-07 18:13 ` [PATCH v2 net-next 1/2] udp_tunnel: create a fastpath GRO lookup Paolo Abeni
2025-03-08 18:37 ` Willem de Bruijn
2025-03-09 15:55 ` Paolo Abeni
2025-03-10 3:51 ` Willem de Bruijn
2025-03-10 11:29 ` Paolo Abeni
2025-03-07 18:13 ` [PATCH v2 net-next 2/2] udp_tunnel: use static call for GRO hooks when possible Paolo Abeni
2025-03-08 18:40 ` Willem de Bruijn
2025-03-09 15:57 ` Paolo Abeni
2025-03-10 3:30 ` Willem de Bruijn [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=67ce5ce1722a4_20941f294a0@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=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;
as well as URLs for NNTP newsgroup(s).