2019-06-13 15:11:47

by Peter Zijlstra

[permalink] [raw]
Subject: [PATCH v2 0/5] x86/percpu semantics and fixes

Hi all,

I still have these patches sitting in my queue and figured I'd repost them.

Last time Linus proposed a "+m" alternative approach, but that generates far
far worse code (I've lost the patch and not re-ran those numbers, but I suppose
I can redo if found important).

These patches have been through 0day for a while.


2019-06-13 18:50:33

by Nadav Amit

[permalink] [raw]
Subject: Re: [PATCH v2 0/5] x86/percpu semantics and fixes

> On Jun 13, 2019, at 6:54 AM, Peter Zijlstra <[email protected]> wrote:
>
> Hi all,
>
> I still have these patches sitting in my queue and figured I'd repost them.
>
> Last time Linus proposed a "+m" alternative approach, but that generates far
> far worse code (I've lost the patch and not re-ran those numbers, but I suppose
> I can redo if found important).

I remember I tried it as well and got the same results.

> These patches have been through 0day for a while.

Finally, I would not need to cache smp_processor_id() on the stack when it
is used multiple times…