Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759811Ab1FAVkZ (ORCPT ); Wed, 1 Jun 2011 17:40:25 -0400 Received: from cantor.suse.de ([195.135.220.2]:43563 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758929Ab1FAVkY (ORCPT ); Wed, 1 Jun 2011 17:40:24 -0400 Date: Wed, 1 Jun 2011 22:40:18 +0100 From: Mel Gorman To: Andrea Arcangeli Cc: Minchan Kim , akpm@linux-foundation.org, Ury Stankevich , KOSAKI Motohiro , linux-kernel@vger.kernel.org, linux-mm@kvack.org, stable@kernel.org Subject: Re: [PATCH] mm: compaction: Abort compaction if too many pages are isolated and caller is asynchronous Message-ID: <20110601214018.GC7306@suse.de> References: <20110530153748.GS5044@csn.ul.ie> <20110530165546.GC5118@suse.de> <20110530175334.GI19505@random.random> <20110531121620.GA3490@barrios-laptop> <20110531122437.GJ19505@random.random> <20110531133340.GB3490@barrios-laptop> <20110531141402.GK19505@random.random> <20110601005747.GC7019@csn.ul.ie> <20110601175809.GB7306@suse.de> <20110601191529.GY19505@random.random> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20110601191529.GY19505@random.random> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1423 Lines: 33 On Wed, Jun 01, 2011 at 09:15:29PM +0200, Andrea Arcangeli wrote: > On Wed, Jun 01, 2011 at 06:58:09PM +0100, Mel Gorman wrote: > > Umm, HIGHMEM4G implies a two-level pagetable layout so where are > > things like _PAGE_BIT_SPLITTING being set when THP is enabled? > > They should be set on the pgd, pud_offset/pgd_offset will just bypass. > The splitting bit shouldn't be special about it, the present bit > should work the same. This comment is misleading at best then. #define _PAGE_BIT_SPLITTING _PAGE_BIT_UNUSED1 /* only valid on a PSE pmd */ At the PGD level, it can have PSE set obviously but it's not a PMD. I confess I haven't checked the manual to see if it's safe to use _PAGE_BIT_UNUSED1 like this so am taking your word for it. I found that the bug is far harder to reproduce with 3 pagetable levels than with 2 but that is just timing. So far it has proven impossible on x86-64 at least within 27 hours so that has me looking at how pagetable management between x86 and x86-64 differ. Barriers are a big different between how 32-bit !SMP and X86-64 but don't know yet which one is relevant or if this is even the right direction. -- Mel Gorman SUSE Labs -- 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/