You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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>		18 years ago
..
Makefile	…
extable.c	…
fault.c	header cleaning: don't include smp_lock.h when not used	18 years ago
init.c	x86_64: allocate sparsemem memmap above 4G	18 years ago
ioremap.c	Revert "[PATCH] x86: __pa and __pa_symbol address space separation"	18 years ago
k8topology.c	[PATCH] x86-64: Don't enable NUMA for a single node in K8 NUMA scanning	18 years ago
mmap.c	…
numa.c	[PATCH] x86-64: set node_possible_map at runtime - try 2	18 years ago
pageattr.c	Revert "[PATCH] x86: __pa and __pa_symbol address space separation"	18 years ago
srat.c	[PATCH] x86-64: set node_possible_map at runtime - try 2	18 years ago