From: Jakub Kicinski <kuba@kernel.org>
To: Caleb Sander <csander@purestorage.com>
Cc: David Miller <davem@davemloft.net>,
Tom Herbert <therbert@google.com>,
Thomas Gleixner <tglx@linutronix.de>, Eli Cohen <elic@nvidia.com>,
Ben Hutchings <ben@decadent.org.uk>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: cpu_rmap maps CPUs to wrong interrupts after reprogramming affinities
Date: Wed, 18 Dec 2024 17:23:21 -0800 [thread overview]
Message-ID: <20241218172321.71ea4b4a@kernel.org> (raw)
In-Reply-To: <CADUfDZpUFmBCJPX+u3GYeyFUbQ3RgqevvCpL=ZE48E4_p_BpPA@mail.gmail.com>
On Fri, 13 Dec 2024 10:18:30 -0800 Caleb Sander wrote:
> I can see a few possible ways to address this:
> - Store the current affinity masks for all the IRQs in struct cpu_rmap
> so the next closest IRQ can be computed when a CPU's closest IRQ is
> invalidated. This would significantly increase the size of struct
> cpu_rmap.
Ahmed is actively working on something along those lines:
https://lore.kernel.org/all/20241218165843.744647-1-ahmed.zaki@intel.com/
hopefully we can leverage it?
next prev parent reply other threads:[~2024-12-19 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 18:18 cpu_rmap maps CPUs to wrong interrupts after reprogramming affinities Caleb Sander
2024-12-19 1:23 ` Jakub Kicinski [this message]
2024-12-19 22:04 ` Ben Hutchings
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=20241218172321.71ea4b4a@kernel.org \
--to=kuba@kernel.org \
--cc=ben@decadent.org.uk \
--cc=csander@purestorage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elic@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tglx@linutronix.de \
--cc=therbert@google.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).