[lkml]   [2019]   [Dec]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH RFC 1/1] genirq: Make threaded handler use irq affinity for managed interrupt
On 2019-12-16 10:47, John Garry wrote:
> On 14/12/2019 13:56, Marc Zyngier wrote:
>> On Fri, 13 Dec 2019 15:43:07 +0000
>> John Garry <> wrote:
>> [...]
>>> john@ubuntu:~$ ./dump-io-irq-affinity
>>> kernel version:
>>> Linux ubuntu 5.5.0-rc1-00003-g7adc5d7ec1ca-dirty #1440 SMP PREEMPT
>>> Fri Dec 13 14:53:19 GMT 2019 aarch64 aarch64 aarch64 GNU/Linux
>>> PCI name is 04:00.0: nvme0n1
>>> irq 56, cpu list 75, effective list 5
>>> irq 60, cpu list 24-28, effective list 10
>> The NUMA selection code definitely gets in the way. And to be
>> honest,
>> this NUMA thing is only there for the benefit of a terminally broken
>> implementation (Cavium ThunderX), which we should have never
>> supported
>> the first place.
>> Let's rework this and simply use the managed affinity whenever
>> available instead. It may well be that it will break TX1, but I care
>> about it just as much as Cavium/Marvell does...
> I'm just wondering if non-managed interrupts should be included in
> the load balancing calculation? Couldn't irqbalance (if active) start
> moving non-managed interrupts around anyway?

But they are, aren't they? See what we do in irq_set_affinity:

+ atomic_inc(per_cpu_ptr(&cpu_lpi_count, cpu));
+ atomic_dec(per_cpu_ptr(&cpu_lpi_count,
+ its_dev->event_map.col_map[id]));

We don't try to "rebalance" anything based on that though, not that
I think we should.

>> Please give this new patch a shot on your system (my D05 doesn't
>> have
>> any managed devices):
> We could consider supporting platform msi managed interrupts, but I
> doubt the value.

It shouldn't be hard to do, and most of the existing code could be
moved to the generic level. As for the value, I'm not convinced
either. For example D05 uses the MBIGEN as an intermediate interrupt
controller, so MSIs are from the PoV of MBIGEN, and not the SAS device
attached to it. Not the best design...

> I quickly tested that in my NVMe env, and I see a performance boost
> of 1055K -> 1206K IOPS. Results at bottom.

OK, that's encouraging.

> Here's the irq mapping dump:


Looks good.

> I'm still getting the CPU lockup (even on CPUs which have a single
> NVMe completion interrupt assigned), which taints these results. That
> lockup needs to be fixed.

Is this interrupt screaming to the point where it prevents the
thread from making forward progress? What if you don't use threaded

> We'll check on our SAS env also. I did already hack something up
> similar to your change and again we saw a boost there.

OK. Please keep me posted. If the result is overall positive, I'll
push this into -next for some soaking.


Jazz is not dead. It just smells funny...

 \ /
  Last update: 2019-12-16 12:41    [W:0.072 / U:1.448 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site