From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [PATCH 1/4] arch: local64_t Date: Fri, 21 May 2010 15:52:29 +0100 Message-ID: <23895.1274453549@redhat.com> References: <20100521135944.884367426@chello.nl> <20100521134205.781916350@chello.nl> Return-path: Received: from mx1.redhat.com ([209.132.183.28]:10684 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754001Ab0EUOxN (ORCPT ); Fri, 21 May 2010 10:53:13 -0400 In-Reply-To: <20100521135944.884367426@chello.nl> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Peter Zijlstra Cc: dhowells@redhat.com, Ingo Molnar , Paul Mackerras , Arnaldo Carvalho de Melo , Frederic Weisbecker , Steven Rostedt , David Miller , Paul Mundt , Will Deacon , Deng-Cheng Zhu , LKML , linux-arch@vger.kernel.org Peter Zijlstra wrote: > + * This is the default implementation, which uses atomic64_t. Which is > + * rather pointless. The whole point behind local64_t is that some processors > + * can perform atomic adds and subtracts in a manner which is atomic wrt IRQs > + * running on this CPU. local64_t allows exploitation of such capabilities. Interesting... What FRV does in atomic64-ops.S should probably be rebranded local64_t, and atomic64_t ops be based on that in non-SMP mode. What I did on FRV was to emulate LL/ST instructions using some of the excessive numbers of conditional bits to do so - but it only works on UP systems. David