[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<168563942418.9709.5547131028372889354.git-patchwork-notify@kernel.org>
Date: Thu, 01 Jun 2023 17:10:24 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, netdev@...r.kernel.org, maciej.fijalkowski@...el.com,
magnus.karlsson@...el.com, ast@...nel.org, daniel@...earbox.net,
hawk@...nel.org, john.fastabend@...il.com, bpf@...r.kernel.org,
simon.horman@...igine.com, chandanx.rout@...el.com
Subject: Re: [PATCH net] ice: recycle/free all of the fragments from multi-buffer
frame
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 31 May 2023 08:44:57 -0700 you wrote:
> From: Maciej Fijalkowski <maciej.fijalkowski@...el.com>
>
> The ice driver caches next_to_clean value at the beginning of
> ice_clean_rx_irq() in order to remember the first buffer that has to be
> freed/recycled after main Rx processing loop. The end boundary is
> indicated by first descriptor of frame that Rx processing loop has ended
> its duties. Note that if mentioned loop ended in the middle of gathering
> multi-buffer frame, next_to_clean would be pointing to the descriptor in
> the middle of the frame BUT freeing/recycling stage will stop at the
> first descriptor. This means that next iteration of ice_clean_rx_irq()
> will miss the (first_desc, next_to_clean - 1) entries.
>
> [...]
Here is the summary with links:
- [net] ice: recycle/free all of the fragments from multi-buffer frame
https://git.kernel.org/netdev/net/c/abaf8d51b0ce
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