From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([66.187.233.31]:64749 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932123AbWCHTby (ORCPT ); Wed, 8 Mar 2006 14:31:54 -0500 From: David Howells In-Reply-To: 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> <14275.1141844922@warthog.cambridge.redhat.com> Subject: Re: [PATCH] Document Linux's memory barriers [try #2] Date: Wed, 08 Mar 2006 19:31:42 +0000 Message-ID: <19984.1141846302@warthog.cambridge.redhat.com> Sender: linux-arch-owner@vger.kernel.org To: Linus Torvalds Cc: David Howells , Alan Cox , akpm@osdl.org, mingo@redhat.com, linux-arch@vger.kernel.org, linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org List-ID: Linus Torvalds wrote: > Actually, since the different NUMA things may have different paths to the > PCI thing, I don't think even the mmiowb() will really help. It has > nothing to serialize _with_. On NUMA PowerPC, should mmiowb() be a SYNC or an EIEIO instruction then? Those do inter-component synchronisation. David