From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 28 Jun 2005 10:01:21 -0700 (PDT) From: Christoph Lameter Subject: Re: [patch 2] mm: speculative get_page In-Reply-To: <42C17028.6050903@yahoo.com.au> Message-ID: References: <42C0AAF8.5090700@yahoo.com.au> <20050628040608.GQ3334@holomorphy.com> <42C0D717.2080100@yahoo.com.au> <20050627.220827.21920197.davem@davemloft.net> <20050628141903.GR3334@holomorphy.com> <42C17028.6050903@yahoo.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Nick Piggin Cc: William Lee Irwin III , "David S. Miller" , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Anton Blanchard List-ID: On Wed, 29 Jun 2005, Nick Piggin wrote: > But nit picking aside, is it true that we need a load barrier before > unlock? (store barrier I agree with) The ppc64 changeset in question > indicates yes, but I can't quite work out why. There are noises in the > archives about this, but I didn't pinpoint a conclusion... A spinlock may be used to read a consistent set of variables. If load operations would be moved below the spin_unlock then one may get values that have been updated after another process acquired the spinlock. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org