[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <017fd81e113181218b0fe75db737df98@www.loen.fr>
Date: Mon, 09 Dec 2019 15:36:29 +0000
From: Marc Zyngier <maz@...nel.org>
To: Hannes Reinecke <hare@...e.de>
Cc: John Garry <john.garry@...wei.com>, Ming Lei <ming.lei@...hat.com>,
<tglx@...utronix.de>, <chenxiang66@...ilicon.com>,
<bigeasy@...utronix.de>, <linux-kernel@...r.kernel.org>,
<hare@...e.com>, <hch@....de>, <axboe@...nel.dk>,
<bvanassche@....org>, <peterz@...radead.org>, <mingo@...hat.com>
Subject: Re: [PATCH RFC 1/1] genirq: Make threaded handler use irq affinity for managed interrupt
On 2019-12-09 15:25, Hannes Reinecke wrote:
> On 12/9/19 4:17 PM, Marc Zyngier wrote:
>> On 2019-12-09 15:09, Hannes Reinecke wrote:
>> [slight digression]
>>
>>> My idea here is slightly different: can't we leverage SMT?
>>> Most modern CPUs do SMT (I guess even ARM does it nowadays)
>>> (Yes, I know about spectre and things. We're talking performance
>>> here :-)
>> I only know two of those: Cavium TX2 and ARM Neoverse-E1.
>> ARM SMT CPUs are the absolute minority (and I can't say I'm
>> displeased).
>
> Ach, too bad.
>
> Still a nice idea, putting SMT finally to some use ...
But isn't your SMT idea just a special case of providing an affinity
for the thread (and in this case relative to the affinity of the hard
IRQ)?
You could apply the same principle to target any CPU affinity, and
maybe
provide hints for the placement if you're really keen (same L3, for
example).
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists