Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765736AbYCGUPy (ORCPT ); Fri, 7 Mar 2008 15:15:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759678AbYCGUPq (ORCPT ); Fri, 7 Mar 2008 15:15:46 -0500 Received: from relay2.sgi.com ([192.48.171.30]:41687 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1759552AbYCGUPp (ORCPT ); Fri, 7 Mar 2008 15:15:45 -0500 Date: Fri, 7 Mar 2008 12:15:22 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Andrea Arcangeli cc: Peter Zijlstra , Jack Steiner , Nick Piggin , akpm@linux-foundation.org, Robin Holt , Avi Kivity , kvm-devel@lists.sourceforge.net, general@lists.openfabrics.org, Steve Wise , Roland Dreier , Kanoj Sarcar , linux-kernel@vger.kernel.org, linux-mm@kvack.org, daniel.blueman@quadrics.com Subject: Re: [PATCH] 3/4 combine RCU with seqlock to allow mmu notifier methods to sleep (#v9 was 1/4) In-Reply-To: <20080307194728.GP24114@v2.random> Message-ID: References: <20080304133020.GC5301@v2.random> <20080304222030.GB8951@v2.random> <20080307151722.GD24114@v2.random> <20080307152328.GE24114@v2.random> <1204908762.8514.114.camel@twins> <20080307175019.GK24114@v2.random> <1204912895.8514.120.camel@twins> <20080307184552.GL24114@v2.random> <20080307194728.GP24114@v2.random> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 14 On Fri, 7 Mar 2008, Andrea Arcangeli wrote: > This is a replacement for the previously posted 3/4, one of the pieces > to allow the mmu notifier methods to sleep. Looks good. That is what we talked about last week. What guarantees now that we see the cacheline referenced after the cacheline that contains the pointer that was changed? hlist_for_reach does a rcu_dereference with implied memory barrier? So its like EMM? -- 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/