[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160922160749.GD1892@htj.duckdns.org>
Date: Thu, 22 Sep 2016 12:07:49 -0400
From: Tejun Heo <tj@...nel.org>
To: Nicholas Piggin <npiggin@...il.com>
Cc: Christoph Lameter <cl@...ux.com>, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH] percpu: improve generic percpu modify-return
implementation
Hello,
On Thu, Sep 22, 2016 at 02:35:00PM +1000, Nicholas Piggin wrote:
> Well thank you, how about you?
Heh, can't complain. Hope to see you around sometime. It's been
forever.
> Trying a new mail client, sorry. It *seems* to be working now, how's
> this?
Hmm... Still encoded.
> From d0cb9052d6f4c31d24f999b7b0cecb34681eee9b Mon Sep 17 00:00:00 2001
> From: Nicholas Piggin <npiggin@...il.com>
> Date: Wed, 21 Sep 2016 18:23:43 +1000
> Subject: [PATCH] percpu: improve generic percpu modify-return implementations
>
> Some architectures require an additional load to find the address of
> percpu pointers. In some implemenatations, the C aliasing rules do not
> allow the result of that load to be kept over the store that modifies
> the percpu variable, which causes additional loads.
>
> Work around this by finding the pointer first, then operating on that.
>
> It's also possible to mark things as restrict and those kind of games,
> but that can require larger and arch specific changes.
QP-decoded and applied to percpu/for-4.9.
Thanks.
--
tejun
Powered by blists - more mailing lists