Re: [PATCH RFC 1/1] genirq: Make threaded handler use irq affinity for managed interrupt

From: John Garry
Date: Fri Dec 13 2019 - 05:07:27 EST


On 11/12/2019 09:41, John Garry wrote:
On 10/12/2019 18:32, Marc Zyngier wrote:
The ITS code will make the lowest online CPU in the affinity mask
the
target CPU for the interrupt, which may result in some CPUs
handling
so many interrupts.
If what you want is for the*default*Â affinity to be spread around,
that should be achieved pretty easily. Let me have a think about how
to do that.
Cool, I anticipate that it should help my case.

I can also seek out some NVMe cards to see how it would help a more
"generic" scenario.
Can you give the following a go? It probably has all kind of warts on
top of the quality debug information, but I managed to get my D05 and
a couple of guests to boot with it. It will probably eat your data,
so use caution!;-)


Hi Marc,

Ok, we'll give it a spin.

Thanks,
John

Hi Marc,

JFYI, we're still testing this and the patch itself seems to work as intended.

Here's the kernel log if you just want to see how the interrupts are getting assigned:
https://pastebin.com/hh3r810g

For me, I did get a performance boost for NVMe testing, but my colleague Xiang Chen saw a drop for our storage test of interest - that's the HiSi SAS controller. We're trying to make sense of it now.

Thanks,
John


Thanks,

ÂÂÂÂÂÂÂÂÂ M.

diff --git a/drivers/irqchip/irq-gic-v3-its.c
b/drivers/irqchip/irq-gic-v3-its.c
index e05673bcd52b..301ee3bc0602 100644
--- a/drivers/irqchip/irq-gic-v3-its.c
+++ b/drivers/irqchip/irq-gic-v3-its.c
@@ -177,6 +177,8 @@ static DEFINE_IDA(its_vpeid_ida);