From: Joe Damato <joe@dama.to>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
willemdebruijn.kernel@gmail.com, skhawaja@google.com,
sdf@fomichev.me, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 2/3] net: update NAPI threaded config even for disabled NAPIs
Date: Sat, 9 Aug 2025 19:04:40 -0700 [thread overview]
Message-ID: <aJf-ONUg3AKXjcqV@MacBook-Air.local> (raw)
In-Reply-To: <20250809001205.1147153-3-kuba@kernel.org>
On Fri, Aug 08, 2025 at 05:12:04PM -0700, Jakub Kicinski wrote:
> We chose not to have an "unset" state for threaded, and not to wipe
> the NAPI config clean when channels are explicitly disabled.
Yea... I wonder if we could change that now or if it's too late? I think this
is the thing you mentioned that I couldn't recall in my response to the cover
letter.
> This means the persistent config structs "exist" even when their NAPIs
> are not instantiated.
>
> Differently put - the NAPI persistent state lives in the net_device
> (ncfg == struct napi_config):
>
> ,--- [napi 0] - [napi 1]
> [dev] | |
> `--- [ncfg 0] - [ncfg 1]
>
> so say we a device with 2 queues but only 1 enabled:
>
> ,--- [napi 0]
> [dev] |
> `--- [ncfg 0] - [ncfg 1]
>
> now we set the device to threaded=1:
>
> ,---------- [napi 0 (thr:1)]
> [dev(thr:1)] |
> `---------- [ncfg 0 (thr:1)] - [ncfg 1 (thr:?)]
>
> Since [ncfg 1] was not attached to a NAPI during configuration we
> skipped it. If we create a NAPI for it later it will have the old
> setting (presumably disabled). One could argue if this is right
> or not "in principle", but it's definitely not how things worked
> before per-NAPI config..
Thanks for the detailed commit message. I agree that it should probably work
the same now.
> Fixes: 2677010e7793 ("Add support to set NAPI threaded for individual NAPI")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> v2: add missing kdoc
> ---
> include/linux/netdevice.h | 5 ++++-
> net/core/dev.c | 7 ++++++-
> 2 files changed, 10 insertions(+), 2 deletions(-)
Reviewed-by: Joe Damato <joe@dama.to>
next prev parent reply other threads:[~2025-08-10 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 0:12 [PATCH net v2 0/3] net: prevent deadlocks and mis-configuration with per-NAPI threaded config Jakub Kicinski
2025-08-09 0:12 ` [PATCH net v2 1/3] selftests: drv-net: don't assume device has only 2 queues Jakub Kicinski
2025-08-10 2:01 ` Joe Damato
2025-08-09 0:12 ` [PATCH net v2 2/3] net: update NAPI threaded config even for disabled NAPIs Jakub Kicinski
2025-08-10 2:04 ` Joe Damato [this message]
2025-08-09 0:12 ` [PATCH net v2 3/3] net: prevent deadlocks when enabling NAPIs with mixed kthread config Jakub Kicinski
2025-08-10 2:05 ` Joe Damato
2025-08-10 1:59 ` [PATCH net v2 0/3] net: prevent deadlocks and mis-configuration with per-NAPI threaded config Joe Damato
2025-08-11 15:52 ` Jakub Kicinski
2025-08-12 12:50 ` patchwork-bot+netdevbpf
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=aJf-ONUg3AKXjcqV@MacBook-Air.local \
--to=joe@dama.to \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=skhawaja@google.com \
--cc=willemdebruijn.kernel@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