From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, juri.lelli@redhat.com,
tglx@linutronix.de, linux-rt-users@vger.kernel.org,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
sassmann@redhat.com, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net-next] net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT
Date: Thu, 13 May 2021 20:20:10 +0000 [thread overview]
Message-ID: <162093721042.5649.1489711837264906533.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210512214324.hiaiw3e2tzmsygcz@linutronix.de>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 12 May 2021 23:43:24 +0200 you wrote:
> __napi_schedule_irqoff() is an optimized version of __napi_schedule()
> which can be used where it is known that interrupts are disabled,
> e.g. in interrupt-handlers, spin_lock_irq() sections or hrtimer
> callbacks.
>
> On PREEMPT_RT enabled kernels this assumptions is not true. Force-
> threaded interrupt handlers and spinlocks are not disabling interrupts
> and the NAPI hrtimer callback is forced into softirq context which runs
> with interrupts enabled as well.
>
> [...]
Here is the summary with links:
- [net-next] net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT
https://git.kernel.org/netdev/net-next/c/8380c81d5c4f
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:[~2021-05-13 20:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 6:09 [RT] Question about i40e threaded irq Juri Lelli
2021-05-11 6:24 ` Stefan Assmann
2021-05-11 7:46 ` Thomas Gleixner
2021-05-12 21:43 ` [PATCH net-next] net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT Sebastian Andrzej Siewior
2021-05-12 22:28 ` Thomas Gleixner
2021-05-13 0:50 ` Steven Rostedt
2021-05-13 16:43 ` Steven Rostedt
2021-05-14 12:11 ` Thomas Gleixner
2021-05-14 18:56 ` Jakub Kicinski
2021-05-14 19:44 ` Alison Chaiken
2021-05-14 21:53 ` Thomas Gleixner
2021-05-14 20:16 ` Thomas Gleixner
2021-05-14 20:38 ` Jakub Kicinski
2021-05-13 5:12 ` Juri Lelli
2021-05-13 20:20 ` 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=162093721042.5649.1489711837264906533.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=juri.lelli@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sassmann@redhat.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).