From: patchwork-bot+netdevbpf@kernel.org
To: Tianyi Gao <tianyi@cloudflare.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, toke@redhat.com, horms@kernel.org,
bpf@vger.kernel.org, shuah@kernel.org, hawk@kernel.org,
kernel-team@cloudflare.com, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, sdf@fomichev.me,
linux-kselftest@vger.kernel.org, bochaolucky@gmail.com,
toshiaki.makita1@gmail.com, lorenzo@kernel.org
Subject: Re: [PATCH net 0/2] veth: schedule the peer's NAPI after XDP_TX when only GRO is enabled
Date: Thu, 22 Oct 2026 00:30:08 +0000 [thread overview]
Message-ID: <179262900853.1378903.11234441353449708793.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016214217.16942-1-tianyi@cloudflare.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 16 Oct 2026 22:42:15 +0100 you wrote:
> When an XDP program on a veth device returns XDP_TX and the peer has
> GRO enabled but no XDP program, the frames are queued on the peer's
> ring, but the peer's NAPI is never scheduled to process them. Once the
> ring is full, every XDP_TX frame is dropped.
>
> Commit 0e672f306a28 ("veth: check for NAPI instead of xdp_prog before
> xmit of XDP frame") made such a peer work as an XDP_REDIRECT target,
> where veth_xdp_xmit() both queues the frames and schedules the peer's
> NAPI. XDP_TX queues its frames through the same function but schedules
> the NAPI in veth_xdp_flush(), which still checks xdp_prog.
>
> [...]
Here is the summary with links:
- [net,1/2] veth: schedule the peer's NAPI after XDP_TX when only GRO is enabled
https://git.kernel.org/netdev/net/c/f16b8c6a656e
- [net,2/2] selftests: net: veth: test XDP_TX to a peer with GRO enabled
https://git.kernel.org/netdev/net/c/a70575ae9e81
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:[~2026-10-22 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 21:42 [PATCH net 0/2] veth: schedule the peer's NAPI after XDP_TX when only GRO is enabled Tianyi Gao
2026-10-16 21:42 ` [PATCH net 1/2] " Tianyi Gao
2026-10-17 23:32 ` Mohsin Bashir
2026-10-18 9:08 ` Lorenzo Bianconi
2026-10-19 9:58 ` Jesper Dangaard Brouer
2026-10-16 21:42 ` [PATCH net 2/2] selftests: net: veth: test XDP_TX to a peer with GRO enabled Tianyi Gao
2026-10-22 0:30 ` 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=179262900853.1378903.11234441353449708793.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bochaolucky@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=tianyi@cloudflare.com \
--cc=toke@redhat.com \
--cc=toshiaki.makita1@gmail.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