From: patchwork-bot+netdevbpf@kernel.org
To: Mark Bloch <mbloch@nvidia.com>
Cc: steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, chopps@labn.net,
cratiu@nvidia.com, ychemla@nvidia.com, wangfe@google.com,
lucien.xin@gmail.com, dtatulea@nvidia.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net] xfrm: Force software GSO only in tunnel mode
Date: Thu, 20 Mar 2025 14:50:33 +0000 [thread overview]
Message-ID: <174248223302.1795325.5848574485105137769.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250317103205.573927-1-mbloch@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Mon, 17 Mar 2025 12:32:05 +0200 you wrote:
> From: Cosmin Ratiu <cratiu@nvidia.com>
>
> The cited commit fixed a software GSO bug with VXLAN + IPSec in tunnel
> mode. Unfortunately, it is slightly broader than necessary, as it also
> severely affects performance for Geneve + IPSec transport mode over a
> device capable of both HW GSO and IPSec crypto offload. In this case,
> xfrm_output unnecessarily triggers software GSO instead of letting the
> HW do it. In simple iperf3 tests over Geneve + IPSec transport mode over
> a back-2-back pair of NICs with MTU 1500, the performance was observed
> to be up to 6x worse when doing software GSO compared to leaving it to
> the hardware.
>
> [...]
Here is the summary with links:
- [net] xfrm: Force software GSO only in tunnel mode
https://git.kernel.org/netdev/net/c/0aae2867aa60
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-20 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 10:32 [PATCH net] xfrm: Force software GSO only in tunnel mode Mark Bloch
2025-03-17 19:30 ` Xin Long
2025-03-20 15:24 ` Cosmin Ratiu
2025-03-20 18:37 ` Xin Long
2025-03-18 12:37 ` Mark Bloch
2025-03-20 14: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=174248223302.1795325.5848574485105137769.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chopps@labn.net \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=wangfe@google.com \
--cc=ychemla@nvidia.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).