From: patchwork-bot+netdevbpf@kernel.org
To: Praveen Kaligineedi <pkaligineedi@google.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com, shailend@google.com,
willemb@google.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, hramamurthy@google.com,
joshwash@google.com, ziweixiao@google.com,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] gve: trigger RX NAPI instead of TX NAPI in gve_xsk_wakeup
Date: Tue, 31 Dec 2024 01:50:28 +0000 [thread overview]
Message-ID: <173560982825.1484600.10568371889170047273.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241221032807.302244-1-pkaligineedi@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 20 Dec 2024 19:28:06 -0800 you wrote:
> From: Joshua Washington <joshwash@google.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
prev parent reply other threads:[~2024-12-31 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 3:28 [PATCH net] gve: trigger RX NAPI instead of TX NAPI in gve_xsk_wakeup Praveen Kaligineedi
2024-12-31 1: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=173560982825.1484600.10568371889170047273.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=john.fastabend@gmail.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=shailend@google.com \
--cc=stable@vger.kernel.org \
--cc=willemb@google.com \
--cc=ziweixiao@google.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).