[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <475B6D77.6070906@am.sony.com>
Date: Sat, 08 Dec 2007 20:22:15 -0800
From: Geoff Levand <geoffrey.levand@...sony.com>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: Christoph Lameter <clameter@....com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Andy Whitcroft <apw@...dowen.org>,
Yasunori Goto <y-goto@...fujitsu.com>
Subject: sparsemem: Make SPARSEMEM_VMEMMAP selectable
From: Geoff Levand <geoffrey.levand@...sony.com>
SPARSEMEM_VMEMMAP needs to be a selectable config option to
support building the kernel both with and without sparsemem
vmemmap support. This selection is desirable for platforms
which could be configured one way for platform specific
builds and the other for multi-platform builds.
Signed-off-by: Miguel Botón <mboton@...il.com>
Signed-off-by: Geoff Levand <geoffrey.levand@...sony.com>
---
Andrew,
Please consider for 2.6.24.
-Geoff
mm/Kconfig | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -112,18 +112,17 @@ config SPARSEMEM_EXTREME
def_bool y
depends on SPARSEMEM && !SPARSEMEM_STATIC
-#
-# SPARSEMEM_VMEMMAP uses a virtually mapped mem_map to optimise pfn_to_page
-# and page_to_pfn. The most efficient option where kernel virtual space is
-# not under pressure.
-#
config SPARSEMEM_VMEMMAP_ENABLE
def_bool n
config SPARSEMEM_VMEMMAP
- bool
- depends on SPARSEMEM
- default y if (SPARSEMEM_VMEMMAP_ENABLE)
+ bool "Sparse Memory virtual memmap"
+ depends on SPARSEMEM && SPARSEMEM_VMEMMAP_ENABLE
+ default y
+ help
+ SPARSEMEM_VMEMMAP uses a virtually mapped memmap to optimise
+ pfn_to_page and page_to_pfn operations. This is the most
+ efficient option when sufficient kernel resources are available.
# eventually, we can have this option just 'select SPARSEMEM'
config MEMORY_HOTPLUG
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists