From: patchwork-bot+netdevbpf@kernel.org
To: Samiullah Khawaja <skhawaja@google.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, willemb@google.com, almasrymina@google.com,
netdev@vger.kernel.org, joe@dama.to
Subject: Re: [PATCH net-next v3] net: Update threaded state in napi config in netif_set_threaded
Date: Wed, 06 Aug 2025 01:00:06 +0000 [thread overview]
Message-ID: <175444200676.2225004.6755140210461026267.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250804164457.2494390-1-skhawaja@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 4 Aug 2025 16:44:57 +0000 you wrote:
> Commit 2677010e7793 ("Add support to set NAPI threaded for individual
> NAPI") added support to enable/disable threaded napi using netlink. This
> also extended the napi config save/restore functionality to set the napi
> threaded state. This breaks netdev reset for drivers that use napi
> threaded at device level and also use napi config save/restore on
> napi_disable/napi_enable. Basically on netdev with napi threaded enabled
> at device level, a napi_enable call will get stuck trying to stop the
> napi kthread. This is because the napi->config->threaded is set to
> disabled when threaded is enabled at device level.
>
> [...]
Here is the summary with links:
- [net-next,v3] net: Update threaded state in napi config in netif_set_threaded
https://git.kernel.org/netdev/net/c/e6d76268813d
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:[~2025-08-06 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 16:44 [PATCH net-next v3] net: Update threaded state in napi config in netif_set_threaded Samiullah Khawaja
2025-08-06 1: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=175444200676.2225004.6755140210461026267.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhawaja@google.com \
--cc=willemb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.