From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752205AbZH1S7U (ORCPT ); Fri, 28 Aug 2009 14:59:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751919AbZH1S7S (ORCPT ); Fri, 28 Aug 2009 14:59:18 -0400 Received: from terminus.zytor.com ([198.137.202.10]:53227 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751813AbZH1S7S (ORCPT ); Fri, 28 Aug 2009 14:59:18 -0400 Message-ID: <4A9828F4.4040905@zytor.com> Date: Fri, 28 Aug 2009 11:59:00 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3 MIME-Version: 1.0 To: "linux-mm@kvack.org" , linux-arch@vger.kernel.org CC: Suresh Siddha , Ingo Molnar , Thomas Gleixner , "Pallipadi, Venkatesh" , LKML , Jeremy Fitzhardinge , Sam Ravnborg Subject: PG_uncached, CONFIG_EXTENDED_PAGEFLAGS and !NUMA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, I am looking at a patchset by Venkatesh Pallipadi which cleans up a lot of the corner cases in x86 PAT. http://marc.info/?i=cover.1247162373.git.venkatesh.pallipadi@intel.com This patchset pages PG_uncached available to other architectures than IA64 on an opt-in basis. Unfortunately, it means we run out of page flags on X86_32+PAE+SPARSEMEM. Rather than increasing SECTION_SIZE_BITS further, it seems more reasonable to disable CONFIG_EXTENDED_PAGEFLAGS in this case: diff --git a/mm/Kconfig b/mm/Kconfig index c948d4c..fe221c7 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -153,7 +153,7 @@ config MEMORY_HOTREMOVE # config PAGEFLAGS_EXTENDED def_bool y - depends on 64BIT || SPARSEMEM_VMEMMAP || !NUMA || !SPARSEMEM + depends on 64BIT || SPARSEMEM_VMEMMAP || !SPARSEMEM # Heavily threaded applications may benefit from splitting the mm-wide Dropping the !NUMA requirement here seems reasonable, since we already have generic code that handles removing the node number from the page flags when there are too many. We could make this an x86-specific change, but the above generic change would be cleaner in terms of Kconfig complexity. Would people object to this as a general change? -hpa