From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([66.187.233.31]:42199 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932445AbWCHTAF (ORCPT ); Wed, 8 Mar 2006 14:00:05 -0500 From: David Howells In-Reply-To: <20060308184500.GA17716@devserv.devel.redhat.com> References: <20060308184500.GA17716@devserv.devel.redhat.com> <20060308173605.GB13063@devserv.devel.redhat.com> <20060308145506.GA5095@devserv.devel.redhat.com> <31492.1141753245@warthog.cambridge.redhat.com> <29826.1141828678@warthog.cambridge.redhat.com> <9834.1141837491@warthog.cambridge.redhat.com> <11922.1141842907@warthog.cambridge.redhat.com> Subject: Re: [PATCH] Document Linux's memory barriers [try #2] Date: Wed, 08 Mar 2006 18:59:53 +0000 Message-ID: <14067.1141844393@warthog.cambridge.redhat.com> Sender: linux-arch-owner@vger.kernel.org To: Alan Cox 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: Alan Cox wrote: > then on some NUMA infrastructures the order may not be as you expect. Oh, yuck! Okay... does NUMA guarantee the same for ordinary memory accesses inside the critical section? David