[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173560982825.1484600.10568371889170047273.git-patchwork-notify@kernel.org>
Date: Tue, 31 Dec 2024 01:50:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Praveen Kaligineedi <pkaligineedi@...gle.com>
Cc: netdev@...r.kernel.org, jeroendb@...gle.com, shailend@...gle.com,
willemb@...gle.com, andrew+netdev@...n.ch, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, ast@...nel.org,
daniel@...earbox.net, hawk@...nel.org, john.fastabend@...il.com,
hramamurthy@...gle.com, joshwash@...gle.com, ziweixiao@...gle.com,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH net] gve: trigger RX NAPI instead of TX NAPI in gve_xsk_wakeup
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Fri, 20 Dec 2024 19:28:06 -0800 you wrote:
> From: Joshua Washington <joshwash@...gle.com>
>
> Commit ba0925c34e0f ("gve: process XSK TX descriptors as part of RX NAPI")
> moved XSK TX processing to be part of the RX NAPI. However, that commit
> did not include triggering the RX NAPI in gve_xsk_wakeup. This is
> necessary because the TX NAPI only processes TX completions, meaning
> that a TX wakeup would not actually trigger XSK descriptor processing.
> Also, the branch on XDP_WAKEUP_TX was supposed to have been removed, as
> the NAPI should be scheduled whether the wakeup is for RX or TX.
>
> [...]
Here is the summary with links:
- [net] gve: trigger RX NAPI instead of TX NAPI in gve_xsk_wakeup
https://git.kernel.org/netdev/net/c/fb3a9a1165ce
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