Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935728AbXHOSxS (ORCPT ); Wed, 15 Aug 2007 14:53:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754796AbXHOSw5 (ORCPT ); Wed, 15 Aug 2007 14:52:57 -0400 Received: from gate.crashing.org ([63.228.1.57]:42428 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754477AbXHOSwz (ORCPT ); Wed, 15 Aug 2007 14:52:55 -0400 In-Reply-To: <46C140DD.3060509@yahoo.com.au> References: <46BCC26B.6080600@redhat.com> <46BB46B2.60808@redhat.com> <20070809134150.GA14890@shell.boston.redhat.com> <2708.1186737826@redhat.com> <7680.1186822071@redhat.com> <46BFFDBD.6080804@redhat.com> <46C140DD.3060509@yahoo.com.au> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2cbda24e96a49c3ab7cf7039c515f9fc@kernel.crashing.org> Content-Transfer-Encoding: 7bit Cc: heiko.carstens@de.ibm.com, horms@verge.net.au, linux-kernel@vger.kernel.org, rpjday@mindspring.com, ak@suse.de, netdev@vger.kernel.org, cfriesen@nortel.com, akpm@linux-foundation.org, torvalds@linux-foundation.org, jesper.juhl@gmail.com, linux-arch@vger.kernel.org, zlynx@acm.org, schwidefsky@de.ibm.com, Chris Snook , davem@davemloft.net, wensong@linux-vs.org, wjiang@resilience.com, David Howells From: Segher Boessenkool Subject: Re: [PATCH 6/24] make atomic_read() behave consistently on frv Date: Wed, 15 Aug 2007 20:51:58 +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: 833 Lines: 25 > Well if there is only one memory location involved, then smp_rmb() > isn't > going to really do anything anyway, so it would be incorrect to use it. rmb() orders *any* two reads; that includes two reads from the same location. > Consider that smp_rmb basically will do anything from flushing the > pipeline to invalidating loads speculatively executed out of order. > AFAIK > it will not control the visibility of stores coming from other CPUs > (that > is up to the cache coherency). The writer side should typically use wmb() whenever the reader side uses rmb(), sure. 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/