kernel-ark/arch/x86_64/mm
Zou Nan hai 2e1c49db4c x86_64: allocate sparsemem memmap above 4G
On systems with huge amount of physical memory, VFS cache and memory memmap
may eat all available system memory under 4G, then the system may fail to
allocate swiotlb bounce buffer.

There was a fix for this issue in arch/x86_64/mm/numa.c, but that fix dose
not cover sparsemem model.

This patch add fix to sparsemem model by first try to allocate memmap above
4G.

Signed-off-by: Zou Nan hai <nanhai.zou@intel.com>
Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Andi Kleen <ak@suse.de>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-06-01 08:18:27 -07:00
..
extable.c
fault.c header cleaning: don't include smp_lock.h when not used 2007-05-08 11:15:07 -07:00
init.c x86_64: allocate sparsemem memmap above 4G 2007-06-01 08:18:27 -07:00
ioremap.c Revert "[PATCH] x86: __pa and __pa_symbol address space separation" 2007-05-07 08:44:24 -07:00
k8topology.c [PATCH] x86-64: Don't enable NUMA for a single node in K8 NUMA scanning 2007-05-02 19:27:21 +02:00
Makefile
mmap.c
numa.c [PATCH] x86-64: set node_possible_map at runtime - try 2 2007-05-02 19:27:20 +02:00
pageattr.c Revert "[PATCH] x86: __pa and __pa_symbol address space separation" 2007-05-07 08:44:24 -07:00
srat.c [PATCH] x86-64: set node_possible_map at runtime - try 2 2007-05-02 19:27:20 +02:00