Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932241AbWIIOrO (ORCPT ); Sat, 9 Sep 2006 10:47:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932235AbWIIOrO (ORCPT ); Sat, 9 Sep 2006 10:47:14 -0400 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:47794 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S932243AbWIIOrL (ORCPT ); Sat, 9 Sep 2006 10:47:11 -0400 Subject: Re: Opinion on ordering of writel vs. stores to RAM From: Alan Cox To: Benjamin Herrenschmidt Cc: Linus Torvalds , Paul Mackerras , linux-kernel@vger.kernel.org, akpm@osdl.org, segher@kernel.crashing.org, davem@davemloft.net In-Reply-To: <1157786600.31071.166.camel@localhost.localdomain> References: <17666.8433.533221.866510@cargo.ozlabs.ibm.com> <1157786600.31071.166.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Sat, 09 Sep 2006 16:09:51 +0100 Message-Id: <1157814591.6877.29.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 708 Lines: 19 Ar Sad, 2006-09-09 am 17:23 +1000, ysgrifennodd Benjamin Herrenschmidt: > The problem is that very few people have any clear idea of what mmiowb > is :) In fact, what you described is not the definition of mmiowb > according to Jesse Some of us talked a little about this at Linux Kongress and one suggestion so people did understand it was spin_lock_io(); spin_unlock_io(); so that it can be expressed not as a weird barrier op but as part of the locking. - 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/