From: David Woodhouse <dwmw2@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Chris Friesen <chris.friesen@windriver.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Nitesh Narayan Lal <nitesh@redhat.com>
Subject: Re: PCI, isolcpus, and irq affinity
Date: Mon, 12 Oct 2020 21:24:58 +0100 [thread overview]
Message-ID: <cdc531fd18adc46c5642fed456aad25507df5eba.camel@infradead.org> (raw)
In-Reply-To: <87zh4rp7gg.fsf@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Mon, 2020-10-12 at 21:31 +0200, Thomas Gleixner wrote:
> > In this case could disk I/O submitted by one of those CPUs end up
> > interrupting another one?
>
> On older kernels, yes.
>
> X86 enforces effective single CPU affinity for interrupts since v4.15.
Is that here to stay? Because it means that sending external interrupts
in logical mode is kind of pointless, and we might as well do this...
--- a/arch/x86/kernel/apic/x2apic_cluster.c
+++ b/arch/x86/kernel/apic/x2apic_cluster.c
@@ -187,3 +187,3 @@ static struct apic apic_x2apic_cluster __ro_after_init = {
.irq_delivery_mode = dest_Fixed,
- .irq_dest_mode = 1, /* logical */
+ .irq_dest_mode = 0, /* physical */
@@ -205,3 +205,3 @@ static struct apic apic_x2apic_cluster __ro_after_init = {
- .calc_dest_apicid = x2apic_calc_apicid,
+ .calc_dest_apicid = apic_default_calc_apicid,
And then a bunch of things which currently set x2apic_phys just because
of *external* IRQ limitations, no longer have to, and can still benefit
from multicast of IPIs to whole clusters at a time.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2020-10-12 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 15:49 PCI, isolcpus, and irq affinity Chris Friesen
2020-10-12 16:58 ` Bjorn Helgaas
2020-10-12 17:39 ` Sean V Kelley
2020-10-12 19:18 ` Chris Friesen
2020-10-12 17:42 ` Nitesh Narayan Lal
2020-10-12 17:50 ` Thomas Gleixner
2020-10-12 18:58 ` Chris Friesen
2020-10-12 19:07 ` Keith Busch
2020-10-12 19:44 ` Thomas Gleixner
2020-10-15 18:47 ` Chris Friesen
2020-10-15 19:02 ` Keith Busch
2020-10-12 19:31 ` Thomas Gleixner
2020-10-12 20:24 ` David Woodhouse [this message]
2020-10-12 22:25 ` Thomas Gleixner
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=cdc531fd18adc46c5642fed456aad25507df5eba.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=chris.friesen@windriver.com \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nitesh@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).