[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140924165405.GJ16244@arm.com>
Date: Wed, 24 Sep 2014 17:54:06 +0100
From: Will Deacon <will.deacon@....com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"mingo@...nel.org" <mingo@...nel.org>,
"paulmck@...ux.vnet.ibm.com" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH 00/20] arch atomic 'cleanup'
Hi Peter,
On Thu, May 08, 2014 at 02:58:40PM +0100, Peter Zijlstra wrote:
> This series continues the arch atomic rework started with the smp_mb__
> interface cleanup.
>
> In this series we (mostly) reduce the atomic implementations by eliminating
> repetition through use of CPP macros.
>
> A future series will use these macros to implement more atomic ops. With these
> macros we can end up with more atomic ops while the total LoC still shrinks.
>
> Furthermore, rewrite the asm-generic/atomic implementations to require less and
> provide more.
>
> This series is compile tested on a number of archs, but only boot tested on
> x86_64.
What's the status on this series? I'm currently fleshing out an extension to
the atomic API that allows more flexible acquire/release semantics and it
doesn't make sense for me to copy-paste a bunch of code when I could build
it on top of this instead.
Also, do you have any other patches pending in this area? I've lost track...
Cheers,
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists