From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Aaron Tomlin <atomlin@atomlin.com>,
Christoph Hellwig <hch@lst.de>,
Frederic Weisbecker <frederic@kernel.org>,
Jens Axboe <axboe@fb.com>, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@kernel.org>,
Valentin Schneider <vschneid@redhat.com>,
Waiman Long <longman@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [RFC PATCH] Documentation: Add managed interrupts
Date: Mon, 13 Apr 2026 17:53:01 +0200 [thread overview]
Message-ID: <20260413155301.yqgpSjX-@linutronix.de> (raw)
In-Reply-To: <CAFj5m9La5S0B8o677FmHoXkD-N+kMVdJL7Gn1YG5noy_4Q_jxg@mail.gmail.com>
On 2026-04-11 20:18:17 [+0800], Ming Lei wrote:
> > +CPUs listed in the avoided mask remain part of the interrupt’s affinity mask.
> > +This means that if all non‑isolated CPUs go offline while isolated CPUs remain
> > +online, the interrupt will be assigned to one of the isolated CPUs.
>
> Maybe you can add:
>
> In reality it is fine because IO isn't supposed to submit from isolated CPUs.
You can argue both way. And I have some vague memory that block will
schedule kworker and there was some work to use unbound worker instead
of _this_ CPU. I just don't know what happens with interrupt and this is
probably the one thing you can't configure.
Sebastian
next prev parent reply other threads:[~2026-04-13 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 11:02 [RFC PATCH] Documentation: Add managed interrupts Sebastian Andrzej Siewior
2026-04-09 14:32 ` Jonathan Corbet
2026-04-10 15:32 ` Thomas Gleixner
2026-04-11 13:08 ` Jonathan Corbet
2026-04-10 16:59 ` Aaron Tomlin
2026-04-11 12:18 ` Ming Lei
2026-04-13 15:53 ` Sebastian Andrzej Siewior [this message]
2026-04-15 9:05 ` Ming Lei
2026-04-13 10:45 ` Valentin Schneider
2026-04-13 12:19 ` John Ogness
2026-04-13 15:59 ` Sebastian Andrzej Siewior
2026-04-13 15:57 ` Sebastian Andrzej Siewior
2026-04-14 20:10 ` Aaron Tomlin
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=20260413155301.yqgpSjX-@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=atomlin@atomlin.com \
--cc=axboe@fb.com \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=hch@lst.de \
--cc=john.ogness@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=ming.lei@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=vschneid@redhat.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