Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933075AbYAaXKM (ORCPT ); Thu, 31 Jan 2008 18:10:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752602AbYAaXJ6 (ORCPT ); Thu, 31 Jan 2008 18:09:58 -0500 Received: from relay1.sgi.com ([192.48.171.29]:58042 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751732AbYAaXJ6 (ORCPT ); Thu, 31 Jan 2008 18:09:58 -0500 Date: Thu, 31 Jan 2008 15:09:55 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Andrea Arcangeli cc: Robin Holt , Avi Kivity , Izik Eidus , kvm-devel@lists.sourceforge.net, Peter Zijlstra , steiner@sgi.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, daniel.blueman@quadrics.com Subject: Re: [PATCH] mmu notifiers #v5 In-Reply-To: Message-ID: References: <20080131045750.855008281@sgi.com> <20080131171806.GN7185@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: 808 Lines: 20 On Thu, 31 Jan 2008, Christoph Lameter wrote: > > pagefault against the main linux page fault, given we already have all > > needed serialization out of the PT lock. XPMEM is forced to do that > > pt lock cannot serialize with invalidate_range since it is split. A range > requires locking for a series of ptes not only individual ones. Hmmm.. May be okay after all. I see that you are only doing it on the pte level. This means the range callbacks are taking down a max of 512 entries. So you have a callback for each pmd. A callback for 2M of memory? -- 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/