From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:40671 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S932262AbWCGTYp (ORCPT ); Tue, 7 Mar 2006 14:24:45 -0500 From: Andi Kleen Subject: Re: [PATCH] Document Linux's memory barriers Date: Tue, 7 Mar 2006 12:57:23 +0100 References: <200603071134.52962.ak@suse.de> <7621.1141756240@warthog.cambridge.redhat.com> <1141759408.2617.9.camel@serpentine.pathscale.com> In-Reply-To: <1141759408.2617.9.camel@serpentine.pathscale.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603071257.24234.ak@suse.de> Sender: linux-arch-owner@vger.kernel.org To: Bryan O'Sullivan Cc: David Howells , torvalds@osdl.org, akpm@osdl.org, mingo@redhat.com, linux-arch@vger.kernel.org, linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org List-ID: On Tuesday 07 March 2006 20:23, Bryan O'Sullivan wrote: > On Tue, 2006-03-07 at 18:30 +0000, David Howells wrote: > > > True, I suppose. I should make it clear that these accessor functions imply > > memory barriers, if indeed they do, > > They don't, but according to Documentation/DocBook/deviceiobook.tmpl > they are performed by the compiler in the order specified. I don't think that's correct. Probably the documentation should be fixed. -Andi