From: patchwork-bot+netdevbpf@kernel.org
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: davem@davemloft.net, kuba@kernel.org,
herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] xfrm: hold device only for the asynchronous decryption
Date: Thu, 24 Jul 2025 13:30:08 +0000 [thread overview]
Message-ID: <175336380876.2396070.3234412767137065519.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250723080402.3439619-2-steffen.klassert@secunet.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Wed, 23 Jul 2025 10:03:48 +0200 you wrote:
> From: Jianbo Liu <jianbol@nvidia.com>
>
> The dev_hold() on skb->dev during packet reception was originally
> added to prevent the device from being released prematurely during
> asynchronous decryption operations.
>
> As current hardware can offload decryption, this asynchronous path is
> not always utilized. This often results in a pattern of dev_hold()
> immediately followed by dev_put() for each packet, creating
> unnecessary reference counting overhead detrimental to performance.
>
> [...]
Here is the summary with links:
- [1/3] xfrm: hold device only for the asynchronous decryption
https://git.kernel.org/netdev/net-next/c/b05d42eefac7
- [2/3] xfrm: Duplicate SPI Handling
https://git.kernel.org/netdev/net-next/c/94f39804d891
- [3/3] xfrm: Skip redundant statistics update for crypto offload
https://git.kernel.org/netdev/net-next/c/95cfe23285a6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-07-24 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 8:03 [PATCH 0/3] pull request (net-next): ipsec-next 2025-07-23 Steffen Klassert
2025-07-23 8:03 ` [PATCH 1/3] xfrm: hold device only for the asynchronous decryption Steffen Klassert
2025-07-24 13:18 ` Paolo Abeni
2025-07-24 13:30 ` patchwork-bot+netdevbpf [this message]
2025-07-23 8:03 ` [PATCH 2/3] xfrm: Duplicate SPI Handling Steffen Klassert
2025-07-23 8:03 ` [PATCH 3/3] xfrm: Skip redundant statistics update for crypto offload Steffen Klassert
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=175336380876.2396070.3234412767137065519.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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