Re: [PATCH v3 8/9] powerpc/xive: Map one IPI interrupt per node

2021-04-02 Thread Cédric Le Goater
> I gave the patch below a try and we are reaching the same results, > even better. The simplest solution is always the best. Nick, you > should send that single patch. FYI, here are results in a KVM guests with pinned vCPUs. * P9 DD2.2 - 2s * 64 threads - KVM guest :

Re: [PATCH v3 8/9] powerpc/xive: Map one IPI interrupt per node

2021-04-02 Thread Cédric Le Goater
On 4/1/21 2:50 PM, Nicholas Piggin wrote: > Excerpts from Cédric Le Goater's message of April 1, 2021 12:45 am: >> ipistorm [*] can be used to benchmark the raw interrupt rate of an >> interrupt controller by measuring the number of IPIs a system can >> sustain. When applied to the XIVE interrupt c

Re: [PATCH v3 8/9] powerpc/xive: Map one IPI interrupt per node

2021-04-01 Thread Nicholas Piggin
Excerpts from Cédric Le Goater's message of April 1, 2021 12:45 am: > ipistorm [*] can be used to benchmark the raw interrupt rate of an > interrupt controller by measuring the number of IPIs a system can > sustain. When applied to the XIVE interrupt controller of POWER9 and > POWER10 systems, a si

[PATCH v3 8/9] powerpc/xive: Map one IPI interrupt per node

2021-03-31 Thread Cédric Le Goater
ipistorm [*] can be used to benchmark the raw interrupt rate of an interrupt controller by measuring the number of IPIs a system can sustain. When applied to the XIVE interrupt controller of POWER9 and POWER10 systems, a significant drop of the interrupt rate can be observed when crossing the secon