Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762631AbXHQWRn (ORCPT ); Fri, 17 Aug 2007 18:17:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755015AbXHQWR3 (ORCPT ); Fri, 17 Aug 2007 18:17:29 -0400 Received: from gate.crashing.org ([63.228.1.57]:45347 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754374AbXHQWR1 (ORCPT ); Fri, 17 Aug 2007 18:17:27 -0400 In-Reply-To: <46C512EB.7020603@yahoo.com.au> References: <18115.52863.638655.658466@cargo.ozlabs.ibm.com> <20070816053945.GB32442@gondor.apana.org.au> <18115.62741.807704.969977@cargo.ozlabs.ibm.com> <20070816070907.GA964@gondor.apana.org.au> <46C40587.7050708@s5r6.in-berlin.de> <20070816081049.GA1431@gondor.apana.org.au> <46C41EE4.9090806@s5r6.in-berlin.de> <46C42767.4070104@s5r6.in-berlin.de> <20070816104250.GB2927@gondor.apana.org.au> <20070816163441.GB16957@linux.vnet.ibm.com> <46C512EB.7020603@yahoo.com.au> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1f265c14b28f2c5922059a130b1d8aa5@kernel.crashing.org> Content-Transfer-Encoding: 7bit Cc: paulmck@linux.vnet.ibm.com, Christoph Lameter , Paul Mackerras , heiko.carstens@de.ibm.com, Stefan Richter , horms@verge.net.au, Satyam Sharma , Linux Kernel Mailing List , rpjday@mindspring.com, netdev@vger.kernel.org, ak@suse.de, cfriesen@nortel.com, jesper.juhl@gmail.com, linux-arch@vger.kernel.org, Andrew Morton , zlynx@acm.org, schwidefsky@de.ibm.com, Chris Snook , Herbert Xu , davem@davemloft.net, Linus Torvalds , wensong@linux-vs.org, wjiang@resilience.com From: Segher Boessenkool Subject: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures Date: Sat, 18 Aug 2007 00:14:30 +0200 To: Nick Piggin X-Mailer: Apple Mail (2.623) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 551 Lines: 16 > (and yes, it is perfectly legitimate to > want a non-volatile read for a data type that you also want to do > atomic RMW operations on) ...which is undefined behaviour in C (and GCC) when that data is declared volatile, which is a good argument against implementing atomics that way in itself. Segher - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/