From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:5349 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1751675AbWCHAeD (ORCPT ); Tue, 7 Mar 2006 19:34:03 -0500 Subject: Re: [PATCH] Document Linux's memory barriers From: Alan Cox In-Reply-To: <200603072224.09976.ak@suse.de> References: <200603071134.52962.ak@suse.de> <200603071257.24234.ak@suse.de> <1141766085.5255.12.camel@serpentine.pathscale.com> <200603072224.09976.ak@suse.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 08 Mar 2006 00:36:58 +0000 Message-Id: <1141778218.2455.25.camel@localhost.localdomain> Mime-Version: 1.0 Sender: linux-arch-owner@vger.kernel.org To: Andi Kleen Cc: Bryan O'Sullivan , 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 Maw, 2006-03-07 at 22:24 +0100, Andi Kleen wrote: > > But on most arches those accesses do indeed seem to happen in-order. On > > i386 and x86_64, it's a natural consequence of program store ordering. > > Not true for reads on x86. You must have a strange kernel Andi. Mine marks them as volatile unsigned char * references. Alan