From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
horms@kernel.org, dsahern@kernel.org, kuniyu@amazon.com
Subject: Re: [PATCH v4 net-next 0/2] udp_tunnel: GRO optimizations
Date: Tue, 18 Mar 2025 10:50:32 +0000 [thread overview]
Message-ID: <174229503276.4125034.9280386198001897544.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1741718157.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 11 Mar 2025 21:42:27 +0100 you wrote:
> The UDP tunnel GRO stage is source of measurable overhead for workload
> based on UDP-encapsulated traffic: each incoming packets requires a full
> UDP socket lookup and an indirect call.
>
> In the most common setups a single UDP tunnel device is used. In such
> case we can optimize both the lookup and the indirect call.
>
> [...]
Here is the summary with links:
- [v4,net-next,1/2] udp_tunnel: create a fastpath GRO lookup.
https://git.kernel.org/netdev/net-next/c/8d4880db3783
- [v4,net-next,2/2] udp_tunnel: use static call for GRO hooks when possible
https://git.kernel.org/netdev/net-next/c/311b36574cea
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-18 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 20:42 [PATCH v4 net-next 0/2] udp_tunnel: GRO optimizations Paolo Abeni
2025-03-11 20:42 ` [PATCH v4 net-next 1/2] udp_tunnel: create a fastpath GRO lookup Paolo Abeni
2025-03-12 17:46 ` Willem de Bruijn
2025-03-11 20:42 ` [PATCH v4 net-next 2/2] udp_tunnel: use static call for GRO hooks when possible Paolo Abeni
2025-03-12 17:57 ` Willem de Bruijn
2025-03-21 4:16 ` Nathan Chancellor
2025-03-21 9:11 ` Paolo Abeni
2025-03-18 10:50 ` patchwork-bot+netdevbpf [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=174229503276.4125034.9280386198001897544.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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 \
--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.