From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Li Chen <me@linux.beauty>
Cc: arnd bergmann <arnd@arndb.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: Why GICD_ITARGETSR is not used by Linux
Date: Tue, 20 Sep 2022 18:25:29 +0100 [thread overview]
Message-ID: <Yyn3icM5bdy2b3sO@shell.armlinux.org.uk> (raw)
In-Reply-To: <1835b8bd957.c0097d5d1453526.2223557782083902488@linux.beauty>
On Tue, Sep 20, 2022 at 05:37:15PM +0200, Li Chen wrote:
> Hi Russell,
>
> ---- On Tue, 20 Sep 2022 12:09:38 +0200 Russell King (Oracle) wrote ---
> > On ARM, we don't have that. We have a thundering herd of CPUs if we
> > set more than one CPU to process the interrupt, which is grossly
> > inefficient.
>
> So, on arm chips with PCIe controller(s), we also rely on irqbalance to
> distribute endpoints' legacy irq/MSI/MSIx?
I think irqbalance 1.x was functional for all IRQs, not just PCIe.
However, yes, doing it in userspace at this point is the best
solution anyway, IMHO, as it is possible to create whatever policies
one desires there - and what works for one workload may not be good
for another workload.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-20 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 1:42 Why GICD_ITARGETSR is not used by Linux Li Chen
2022-09-20 7:04 ` Arnd Bergmann
2022-09-20 9:45 ` Li Chen
2022-09-20 10:09 ` Russell King (Oracle)
2022-09-20 10:14 ` Russell King (Oracle)
2022-09-21 2:34 ` Li Chen
2022-09-21 7:26 ` Russell King (Oracle)
2022-09-21 7:45 ` Li Chen
2022-09-20 15:37 ` Li Chen
2022-09-20 17:25 ` Russell King (Oracle) [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=Yyn3icM5bdy2b3sO@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=me@linux.beauty \
/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).