From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Sean Anderson <sean.anderson@linux.dev>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Brett Creeley <bcreeley@amd.com>,
Xiang wangx <wangxiang@cdjrlc.com>,
Shaomin Deng <dengshaomin@cdjrlc.com>
Subject: Re: [PATCH net] doc: net: napi: Update documentation for napi_schedule_irqoff
Date: Tue, 1 Oct 2024 08:29:25 +0700 [thread overview]
Message-ID: <ZvtQdSkTGHTBU1qv@archie.me> (raw)
In-Reply-To: <20240930153955.971657-1-sean.anderson@linux.dev>
[-- 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 --]
next prev parent reply other threads:[~2024-10-01 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2024-10-01 6:52 ` Sebastian Andrzej Siewior
2024-10-03 10:20 ` 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=ZvtQdSkTGHTBU1qv@archie.me \
--to=bagasdotme@gmail.com \
--cc=bcreeley@amd.com \
--cc=bigeasy@linutronix.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dengshaomin@cdjrlc.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.anderson@linux.dev \
--cc=wangxiang@cdjrlc.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;
as well as URLs for NNTP newsgroup(s).