Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 19 Feb 2002 07:39:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 19 Feb 2002 07:39:32 -0500 Received: from dsl-213-023-040-169.arcor-ip.net ([213.23.40.169]:29080 "EHLO starship.berlin") by vger.kernel.org with ESMTP id ; Tue, 19 Feb 2002 07:39:19 -0500 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: Hugh Dickins Subject: Re: [RFC] Page table sharing Date: Tue, 19 Feb 2002 13:43:50 +0100 X-Mailer: KMail [version 1.3.2] Cc: Linus Torvalds , Rik van Riel , dmccr@us.ibm.com, Kernel Mailing List , linux-mm@kvack.org, Robert Love , mingo@redhat.co, Andrew Morton , manfred@colorfullife.com, wli@holomorphy.com In-Reply-To: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On February 19, 2002 01:22 pm, Hugh Dickins wrote: > On Tue, 19 Feb 2002, Daniel Phillips wrote: > > On February 19, 2002 04:22 am, Linus Torvalds wrote: > > > That still leaves the TLB invalidation issue, but we could handle that > > > with an alternate approach: use the same "free_pte_ctx" kind of gathering > > > that the zap_page_range() code uses for similar reasons (ie gather up the > > > pte entries that you're going to free first, and then do a global > > > invalidate later). > > > > I think I'll fall back to unsharing the page table on swapout as Hugh > > suggested, until we sort this out. > > My proposal was to unshare the page table on read fault, to avoid race. > I suppose you could, just for your current testing, use that technique > in swapout, to avoid the much more serious TLB issue that Linus has now > raised. But don't do so without realizing that it is a very deadlocky > idea for swapout (making pages freeable) to need to allocate pages. I didn't fail to notice that. It's no worse than any other page reservation issue, of which we have plenty. One day we're going to have to solve them all. > And it's not much use for swapout to skip them either, since the shared > page tables become valuable on the very large address spaces which we'd > want swapout to be hitting. Unsharing is the route of least resistance at the moment. If necessary I can keep a page around for that purpose, then reestablish that reserve after using it. -- Daniel - 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/