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, horms@kernel.org,
hramamurthy@google.com, joshwash@google.com,
ziweixiao@google.com, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net 0/5] gve: various XDP fixes
Date: Fri, 20 Dec 2024 13:00:34 +0000 [thread overview]
Message-ID: <173469963470.2895973.2113580557517865563.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241218133415.3759501-1-pkaligineedi@google.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 18 Dec 2024 05:34:10 -0800 you wrote:
> From: Joshua Washington <joshwash@google.com>
>
> This patch series contains the following XDP fixes:
> - clean up XDP tx queue when stopping rings
> - use RCU synchronization to guard existence of XDP queues
> - perform XSK TX as part of RX NAPI to fix busy polling
> - fix XDP allocation issues when non-XDP configurations occur
>
> [...]
Here is the summary with links:
- [net,1/5] gve: clean XDP queues in gve_tx_stop_ring_gqi
https://git.kernel.org/netdev/net/c/6321f5fb70d5
- [net,2/5] gve: guard XDP xmit NDO on existence of xdp queues
https://git.kernel.org/netdev/net/c/ff7c2dea9dd1
- [net,3/5] gve: guard XSK operations on the existence of queues
https://git.kernel.org/netdev/net/c/40338d7987d8
- [net,4/5] gve: process XSK TX descriptors as part of RX NAPI
https://git.kernel.org/netdev/net/c/ba0925c34e0f
- [net,5/5] gve: fix XDP allocation path in edge cases
https://git.kernel.org/netdev/net/c/de63ac44a527
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-20 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 13:34 [PATCH net 0/5] gve: various XDP fixes Praveen Kaligineedi
2024-12-18 13:34 ` [PATCH net 1/5] gve: clean XDP queues in gve_tx_stop_ring_gqi Praveen Kaligineedi
2024-12-18 13:34 ` [PATCH net 2/5] gve: guard XDP xmit NDO on existence of xdp queues Praveen Kaligineedi
2024-12-18 15:30 ` Alexander Lobakin
2025-01-02 18:43 ` Joshua Washington
2024-12-18 13:34 ` [PATCH net 3/5] gve: guard XSK operations on the existence of queues Praveen Kaligineedi
2024-12-19 17:34 ` Larysa Zaremba
2024-12-18 13:34 ` [PATCH net 4/5] gve: process XSK TX descriptors as part of RX NAPI Praveen Kaligineedi
2024-12-18 13:34 ` [PATCH net 5/5] gve: fix XDP allocation path in edge cases Praveen Kaligineedi
2024-12-20 13:00 ` 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=173469963470.2895973.2113580557517865563.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=horms@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=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