From: Jakub Kicinski <kuba@kernel.org>
To: Tianyi Gao <tianyi@cloudflare.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
toke@redhat.com, lorenzo@kernel.org, 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, jiayuan.chen@linux.dev
Subject: Re: [PATCH net-next 0/3] veth: link RX queues to their NAPI instances
Date: Tue, 10 Nov 2026 17:08:55 -0800 [thread overview]
Message-ID: <20261110170855.5b05db3c@kernel.org> (raw)
In-Reply-To: <20261105143356.17062-1-tianyi@cloudflare.com>
On Thu, 5 Nov 2026 14:33:53 +0000 Tianyi Gao wrote:
> veth does not link its RX queues to their NAPI instances. queue-get
> therefore reports no napi-id for them. napi-get lists the NAPI instances
> of a veth, and their thread PIDs when NAPI is threaded. It does not show
> which RX queue each instance polls. Userspace cannot tell which NAPI
> thread to pin for a given queue, or which NAPI to change with napi-set.
The test does not apply, series needs a respin
--
pw-bot: cr
prev parent reply other threads:[~2026-11-11 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 14:33 [PATCH net-next 0/3] veth: link RX queues to their NAPI instances Tianyi Gao
2026-11-05 14:33 ` [PATCH net-next 1/3] veth: refactor NAPI enable paths Tianyi Gao
2026-11-05 14:33 ` [PATCH net-next 2/3] veth: link RX queues to their NAPI instances Tianyi Gao
2026-11-05 14:33 ` [PATCH net-next 3/3] selftests: net: veth: test RX queue NAPI links Tianyi Gao
2026-11-11 1:08 ` Jakub Kicinski [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=20261110170855.5b05db3c@kernel.org \
--to=kuba@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=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@cloudflare.com \
--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 \
/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