Netdev List
 help / color / mirror / Atom feed
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, lorenzo@kernel.org,
	horms@kernel.org, shuah@kernel.org, ast@kernel.org,
	daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
	sdf@fomichev.me, joe@dama.to, linux-kselftest@vger.kernel.org,
	bpf@vger.kernel.org, kernel-team@cloudflare.com,
	tianyi.gao@linux.dev
Subject: Re: [PATCH net-next v3 0/5] veth: link RX queues to their NAPI instances
Date: Thu, 19 Nov 2026 23:00:09 +0000	[thread overview]
Message-ID: <179512920952.3911009.243890206778536445.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261115193531.57679-1-tianyi@cloudflare.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun, 15 Nov 2026 19:35:26 +0000 you wrote:
> veth does not link its RX queues to their NAPI instances, so queue-get
> reports no napi-id for them. napi-get lists each NAPI instance, and its
> thread PID when NAPI is threaded, but not the RX queue it polls.
> Userspace cannot tell which NAPI thread to pin for a given queue, or
> which NAPI to change with napi-set.
> 
> There is also no way to busy poll an AF_XDP socket bound to a veth
> queue. xsk_bind() takes the socket's NAPI ID from the RX queue, and a
> veth RX queue has none.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/5] veth: refactor NAPI enable paths
    https://git.kernel.org/netdev/net-next/c/774a5a756d20
  - [net-next,v3,2/5] veth: link RX queues to their NAPI instances
    https://git.kernel.org/netdev/net-next/c/c6d21717a602
  - [net-next,v3,3/5] selftests: net: veth: test RX queue NAPI links
    https://git.kernel.org/netdev/net-next/c/5335fdbafea2
  - [net-next,v3,4/5] veth: use persistent NAPI config
    https://git.kernel.org/netdev/net-next/c/3c04f86ffab9
  - [net-next,v3,5/5] selftests: net: veth: test that RX queues keep their NAPI IDs
    https://git.kernel.org/netdev/net-next/c/59bbe682d4b1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-19 23:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15 19:35 [PATCH net-next v3 0/5] veth: link RX queues to their NAPI instances Tianyi Gao
2026-11-15 19:35 ` [PATCH net-next v3 1/5] veth: refactor NAPI enable paths Tianyi Gao
2026-11-15 19:35 ` [PATCH net-next v3 2/5] veth: link RX queues to their NAPI instances Tianyi Gao
2026-11-15 19:35 ` [PATCH net-next v3 3/5] selftests: net: veth: test RX queue NAPI links Tianyi Gao
2026-11-15 19:35 ` [PATCH net-next v3 4/5] veth: use persistent NAPI config Tianyi Gao
2026-11-15 19:35 ` [PATCH net-next v3 5/5] selftests: net: veth: test that RX queues keep their NAPI IDs Tianyi Gao
2026-11-19 23: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=179512920952.3911009.243890206778536445.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@kernel.org \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=joe@dama.to \
    --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.gao@linux.dev \
    --cc=tianyi@cloudflare.com \
    --cc=toke@redhat.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