* [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff
@ 2024-09-30 15:39 Sean Anderson
2024-10-01 1:29 ` Bagas Sanjaya
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Sean Anderson @ 2024-09-30 15:39 UTC (permalink / raw)
To: David S . Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
netdev
Cc: Sebastian Andrzej Siewior, linux-doc, linux-kernel,
Jonathan Corbet, Brett Creeley, Sean Anderson
Since commit 8380c81d5c4f ("net: Treat __napi_schedule_irqoff() as
__napi_schedule() on PREEMPT_RT"), napi_schedule_irqoff will do the
right thing if IRQs are threaded. Therefore, there is no need to use
IRQF_NO_THREAD.
Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
---
https://lore.kernel.org/netdev/20240913150954.2287196-1-sean.anderson@linux.dev/
Documentation/networking/napi.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/networking/napi.rst b/Documentation/networking/napi.rst
index 7bf7b95c4f7a..dfa5d549be9c 100644
--- a/Documentation/networking/napi.rst
+++ b/Documentation/networking/napi.rst
@@ -144,9 +144,8 @@ IRQ should only be unmasked after a successful call to napi_complete_done():
napi_schedule_irqoff() is a variant of napi_schedule() which takes advantage
of guarantees given by being invoked in IRQ context (no need to
-mask interrupts). Note that PREEMPT_RT forces all interrupts
-to be threaded so the interrupt may need to be marked ``IRQF_NO_THREAD``
-to avoid issues on real-time kernel configurations.
+mask interrupts). napi_schedule_irqoff() will fall back to napi_schedule() if
+IRQs are threaded (such as if ``PREEMPT_RT`` is enabled).
Instance to queue mapping
-------------------------
--
2.35.1.1320.gc452695387.dirty
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff
2024-09-30 15:39 [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff Sean Anderson
@ 2024-10-01 1:29 ` Bagas Sanjaya
2024-10-01 6:52 ` Sebastian Andrzej Siewior
2024-10-03 10:20 ` patchwork-bot+netdevbpf
2 siblings, 0 replies; 4+ messages in thread
From: Bagas Sanjaya @ 2024-10-01 1:29 UTC (permalink / raw)
To: Sean Anderson, David S . Miller, Eric Dumazet, Jakub Kicinski,
Paolo Abeni, netdev
Cc: Sebastian Andrzej Siewior, linux-doc, linux-kernel,
Jonathan Corbet, Brett Creeley, Xiang wangx, Shaomin Deng
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
On Mon, Sep 30, 2024 at 11:39:54AM -0400, Sean Anderson wrote:
> napi_schedule_irqoff() is a variant of napi_schedule() which takes advantage
> of guarantees given by being invoked in IRQ context (no need to
> -mask interrupts). Note that PREEMPT_RT forces all interrupts
> -to be threaded so the interrupt may need to be marked ``IRQF_NO_THREAD``
> -to avoid issues on real-time kernel configurations.
> +mask interrupts). napi_schedule_irqoff() will fall back to napi_schedule() if
> +IRQs are threaded (such as if ``PREEMPT_RT`` is enabled).
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff
2024-09-30 15:39 [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff Sean Anderson
2024-10-01 1:29 ` Bagas Sanjaya
@ 2024-10-01 6:52 ` Sebastian Andrzej Siewior
2024-10-03 10:20 ` patchwork-bot+netdevbpf
2 siblings, 0 replies; 4+ messages in thread
From: Sebastian Andrzej Siewior @ 2024-10-01 6:52 UTC (permalink / raw)
To: Sean Anderson
Cc: David S . Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
netdev, linux-doc, linux-kernel, Jonathan Corbet, Brett Creeley
On 2024-09-30 11:39:54 [-0400], Sean Anderson wrote:
> Since commit 8380c81d5c4f ("net: Treat __napi_schedule_irqoff() as
> __napi_schedule() on PREEMPT_RT"), napi_schedule_irqoff will do the
> right thing if IRQs are threaded. Therefore, there is no need to use
> IRQF_NO_THREAD.
>
> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Thanks for docs update.
Sebastian
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff
2024-09-30 15:39 [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff Sean Anderson
2024-10-01 1:29 ` Bagas Sanjaya
2024-10-01 6:52 ` Sebastian Andrzej Siewior
@ 2024-10-03 10:20 ` patchwork-bot+netdevbpf
2 siblings, 0 replies; 4+ messages in thread
From: patchwork-bot+netdevbpf @ 2024-10-03 10:20 UTC (permalink / raw)
To: Sean Anderson
Cc: davem, edumazet, kuba, pabeni, netdev, bigeasy, linux-doc,
linux-kernel, corbet, bcreeley
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 30 Sep 2024 11:39:54 -0400 you wrote:
> Since commit 8380c81d5c4f ("net: Treat __napi_schedule_irqoff() as
> __napi_schedule() on PREEMPT_RT"), napi_schedule_irqoff will do the
> right thing if IRQs are threaded. Therefore, there is no need to use
> IRQF_NO_THREAD.
>
> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
>
> [...]
Here is the summary with links:
- [net] doc: net: napi: Update documentation for napi_schedule_irqoff
https://git.kernel.org/netdev/net/c/b63ad06ddddf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-10-03 10:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-09-30 15:39 [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff Sean Anderson
2024-10-01 1:29 ` Bagas Sanjaya
2024-10-01 6:52 ` Sebastian Andrzej Siewior
2024-10-03 10:20 ` patchwork-bot+netdevbpf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).