Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936175AbXHOT7a (ORCPT ); Wed, 15 Aug 2007 15:59:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1765793AbXHOT7I (ORCPT ); Wed, 15 Aug 2007 15:59:08 -0400 Received: from netops-testserver-4-out.sgi.com ([192.48.171.29]:43683 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1764310AbXHOT7F (ORCPT ); Wed, 15 Aug 2007 15:59:05 -0400 Date: Wed, 15 Aug 2007 12:59:01 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Stefan Richter cc: Satyam Sharma , Chris Snook , Linux Kernel Mailing List , linux-arch@vger.kernel.org, torvalds@linux-foundation.org, netdev@vger.kernel.org, Andrew Morton , ak@suse.de, heiko.carstens@de.ibm.com, davem@davemloft.net, schwidefsky@de.ibm.com, wensong@linux-vs.org, horms@verge.net.au, wjiang@resilience.com, cfriesen@nortel.com, zlynx@acm.org, rpjday@mindspring.com, jesper.juhl@gmail.com, segher@kernel.crashing.org, Herbert Xu , "Paul E. McKenney" Subject: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures In-Reply-To: <46C2D6F3.3070707@s5r6.in-berlin.de> Message-ID: References: <20070809131423.GA9927@shell.boston.redhat.com> <46C2D6F3.3070707@s5r6.in-berlin.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 623 Lines: 17 On Wed, 15 Aug 2007, Stefan Richter wrote: > LDD3 says on page 125: "The following operations are defined for the > type [atomic_t] and are guaranteed to be atomic with respect to all > processors of an SMP computer." > > Doesn't "atomic WRT all processors" require volatility? Atomic operations only require exclusive access to the cacheline while the value is modified. - 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/