[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175336380876.2396070.3234412767137065519.git-patchwork-notify@kernel.org>
Date: Thu, 24 Jul 2025 13:30:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Steffen Klassert <steffen.klassert@...unet.com>
Cc: davem@...emloft.net, kuba@...nel.org, herbert@...dor.apana.org.au,
netdev@...r.kernel.org
Subject: Re: [PATCH 1/3] xfrm: hold device only for the asynchronous
decryption
Hello:
This series was applied to netdev/net-next.git (main)
by Steffen Klassert <steffen.klassert@...unet.com>:
On Wed, 23 Jul 2025 10:03:48 +0200 you wrote:
> From: Jianbo Liu <jianbol@...dia.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
Powered by blists - more mailing lists