mm: remove !NUMA condition from PAGEFLAGS_EXTENDED condition set
authorH. Peter Anvin <hpa@zytor.com>
Mon, 31 Aug 2009 18:17:44 +0000 (11:17 -0700)
committerH. Peter Anvin <hpa@zytor.com>
Mon, 31 Aug 2009 18:17:44 +0000 (11:17 -0700)
commita269cca9926faf8e44b340b017be0d884203141b
tree992a9ab46250d958d9663fd5b64479c95fbe7732
parent47d25003cbd9e9030a95f7ccc4e70fec6aa7b844
mm: remove !NUMA condition from PAGEFLAGS_EXTENDED condition set

CONFIG_PAGEFLAGS_EXTENDED disables a trick to conserve pageflags.
This trick is indended to be enabled when the pressure on page flags
is very high.

The previous condition was:

-       depends on 64BIT || SPARSEMEM_VMEMMAP || !NUMA || !SPARSEMEM

... however, the sparsemem code already has a way to crowd out the
node number from the pageflags, which means that !NUMA actually
doesn't contribute to hard pageflags exhaustion.

This is required for the new PG_uncached flag to not cause pageflags
exhaustion on x86_32 + PAE + SPARSEMEM + !NUMA.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
LKML-Reference: <4A9828F4.4040905@zytor.com>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Suresh Siddha <suresh.siddha@intel.com>
mm/Kconfig