From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, horms@kernel.org, donald.hunter@gmail.com,
andrew+netdev@lunn.ch, shuah@kernel.org,
willemdebruijn.kernel@gmail.com, sdf@fomichev.me,
petrm@nvidia.com, razor@blackwall.org, idosch@nvidia.com
Subject: Re: [PATCH v5 net-next 00/10] geneve: introduce double tunnel GSO/GRO support
Date: Fri, 23 Jan 2026 19:50:30 +0000 [thread overview]
Message-ID: <176919783084.2695110.88149149748151236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1769011015.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Jan 2026 17:11:26 +0100 you wrote:
> This is the [belated] incarnation of topic discussed in the last Neconf
> [1].
>
> In container orchestration in virtual environments there is a consistent
> usage of double UDP tunneling - specifically geneve. Such setup lack
> support of GRO and GSO for inter VM traffic.
>
> [...]
Here is the summary with links:
- [v5,net-next,01/10] net: introduce mangleid_features
https://git.kernel.org/netdev/net-next/c/31c5a71d982b
- [v5,net-next,02/10] geneve: expose gso partial features for tunnel offload
https://git.kernel.org/netdev/net-next/c/0c09e89f6cea
- [v5,net-next,03/10] vxlan: expose gso partial features for tunnel offload
https://git.kernel.org/netdev/net-next/c/e0b73b5a9257
- [v5,net-next,04/10] geneve: add netlink support for GRO hint
https://git.kernel.org/netdev/net-next/c/ba1b8c97b9a0
- [v5,net-next,05/10] geneve: constify geneve_hlen()
https://git.kernel.org/netdev/net-next/c/759b8d3cef7b
- [v5,net-next,06/10] geneve: pass the geneve device ptr to geneve_build_skb()
https://git.kernel.org/netdev/net-next/c/1da80d91bd0e
- [v5,net-next,07/10] geneve: add GRO hint output path
https://git.kernel.org/netdev/net-next/c/e0a12cbf262b
- [v5,net-next,08/10] geneve: extract hint option at GRO stage
https://git.kernel.org/netdev/net-next/c/0eaf63b3fcda
- [v5,net-next,09/10] geneve: use GRO hint option in the RX path
https://git.kernel.org/netdev/net-next/c/fd0dd796576e
- [v5,net-next,10/10] selftests: net: tests for add double tunneling GRO/GSO
https://git.kernel.org/netdev/net-next/c/40146bf7555e
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:[~2026-01-23 19:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 16:11 [PATCH v5 net-next 00/10] geneve: introduce double tunnel GSO/GRO support Paolo Abeni
2026-01-21 16:11 ` [PATCH v5 net-next 01/10] net: introduce mangleid_features Paolo Abeni
2026-01-21 16:15 ` Eric Dumazet
2026-01-23 19:32 ` Jakub Kicinski
2026-01-21 16:11 ` [PATCH v5 net-next 02/10] geneve: expose gso partial features for tunnel offload Paolo Abeni
2026-01-21 16:11 ` [PATCH v5 net-next 03/10] vxlan: " Paolo Abeni
2026-01-21 16:11 ` [PATCH v5 net-next 04/10] geneve: add netlink support for GRO hint Paolo Abeni
2026-01-21 16:11 ` [PATCH v5 net-next 05/10] geneve: constify geneve_hlen() Paolo Abeni
2026-01-21 16:11 ` [PATCH v5 net-next 06/10] geneve: pass the geneve device ptr to geneve_build_skb() Paolo Abeni
2026-01-21 16:11 ` [PATCH v5 net-next 07/10] geneve: add GRO hint output path Paolo Abeni
2026-01-21 16:11 ` [PATCH v5 net-next 08/10] geneve: extract hint option at GRO stage Paolo Abeni
2026-01-22 14:57 ` Paolo Abeni
2026-01-23 17:54 ` Simon Horman
2026-01-23 17:53 ` [v5,net-next,08/10] " Simon Horman
2026-01-21 16:11 ` [PATCH v5 net-next 09/10] geneve: use GRO hint option in the RX path Paolo Abeni
2026-01-21 16:11 ` [PATCH v5 net-next 10/10] selftests: net: tests for add double tunneling GRO/GSO Paolo Abeni
2026-01-22 10:05 ` Petr Machata
2026-01-23 19:33 ` [PATCH v5 net-next 00/10] geneve: introduce double tunnel GSO/GRO support Jakub Kicinski
2026-01-26 14:15 ` Paolo Abeni
2026-01-23 19: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=176919783084.2695110.88149149748151236.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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.