[lkml]   [2020]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v4 0/2] irqchip/gic-v3-its: Balance LPI affinity across CPUs
When mapping a LPI, the ITS driver picks the first possible
affinity, which is in most cases CPU0, assuming that if
that's not suitable, someone will come and set the affinity
to something more interesting.

It apparently isn't the case, and people complain of poor
performance when many interrupts are glued to the same CPU.
So let's place the interrupts by finding the "least loaded"
CPU (that is, the one that has the fewer LPIs mapped to it).
So called 'managed' interrupts are an interesting case where
the affinity is actually dictated by the kernel itself, and
we should honor this.

* From v3:
- Always pre-decrement/post-increment affinity to avoid useless
changes of affinity (John)
- Don't use the node mask as a superset of the proposed affinity
as the ACPI tables can't really describe this (John)
- Rebased on v5.7-rc5

* From v2:
- Split accounting from CPU selection
- Track managed and unmanaged interrupts separately

Marc Zyngier (2):
irqchip/gic-v3-its: Track LPI distribution on a per CPU basis
irqchip/gic-v3-its: Balance initial LPI affinity across CPUs

drivers/irqchip/irq-gic-v3-its.c | 170 ++++++++++++++++++++++++++-----
1 file changed, 143 insertions(+), 27 deletions(-)


 \ /
  Last update: 2020-05-15 18:58    [W:0.051 / U:2.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site