Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751071AbWCaGSB (ORCPT ); Fri, 31 Mar 2006 01:18:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751092AbWCaGSB (ORCPT ); Fri, 31 Mar 2006 01:18:01 -0500 Received: from e32.co.us.ibm.com ([32.97.110.150]:24007 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S1751071AbWCaGSA (ORCPT ); Fri, 31 Mar 2006 01:18:00 -0500 Date: Thu, 30 Mar 2006 22:18:22 -0800 From: "Paul E. McKenney" To: Jeremy Higdon Cc: bcasavan@sgi.com, Keith Owens , Andi Kleen , ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com, vatsa@in.ibm.com, Oleg Nesterov , linux-kernel@vger.kernel.org, Dipankar Sarma , Andrew Morton , Ingo Molnar Subject: Re: Semantics of smp_mb() [was : Re: [PATCH] Fix RCU race in access of nohz_cpu_mask ] Message-ID: <20060331061822.GC20444@us.ibm.com> Reply-To: paulmck@us.ibm.com References: <20051213162027.GA14158@us.ibm.com> <17158.1134512861@ocs3.ocs.com.au> <20051216074626.GB201289@sgi.com> <20060313183932.GE1297@us.ibm.com> <20060331045627.GB426545@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060331045627.GB426545@sgi.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1769 Lines: 39 On Thu, Mar 30, 2006 at 08:56:27PM -0800, Jeremy Higdon wrote: > On Mon, Mar 13, 2006 at 10:39:32AM -0800, Paul E. McKenney wrote: > > On Thu, Dec 15, 2005 at 11:46:26PM -0800, Jeremy Higdon wrote: > > > Roland Dreier got this right. The purpose of the mmiowb is > > > to ensure that writes to I/O devices while holding a spinlock > > > are ordered with respect to writes issued after the original > > > processor releases and a second processor acquires said > > > spinlock. > > > > > > A MMIO read would be sufficient, but is much heavier weight. > > > > > > On the SGI MIPS-based systems, the "sync" instruction was used. > > > On the Altix systems, a register on the hub chip is read. > > > > > > >From comments by jejb, we're looking at modifying the mmiowb > > > API by adding an argument which would be a register to read > > > from if the architecture in question needs ordering in this > > > way but does not have a lighter weight mechanism like the Altix > > > mmiowb. Since there will now need to be a width indication, > > > mmiowb will be replaced with mmiowb[bwlq]. > > > > Any progress on this front? I figured that I would wait to update > > the ordering document until after this change happened, but if it > > is going to be awhile, I should proceed with the current API. > > > > Thoughts? > > Brent Casavant was going to be working on this. I'll CC him so that > he can indicate the status. David Howells is documenting memory barriers in the Documentation directory as well. Thanx, Paul - 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/