summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorYasunori Goto <y-goto@jp.fujitsu.com>2006-10-28 19:38:32 +0200
committerLinus Torvalds <torvalds@g5.osdl.org>2006-10-28 20:30:52 +0200
commitf2d0aa5bf8d4f7ae4cb1a7feebf5b1afddd0b9b0 (patch)
treef018b4472a40d6ed1d815b68a716f29991993aba /fs
parent[PATCH] md: fix printk format warnings, seen on powerpc64: (diff)
downloadlinux-f2d0aa5bf8d4f7ae4cb1a7feebf5b1afddd0b9b0.tar.xz
linux-f2d0aa5bf8d4f7ae4cb1a7feebf5b1afddd0b9b0.zip
[PATCH] memory hotplug: __GFP_NOWARN is better for __kmalloc_section_memmap()
Add __GFP_NOWARN flag to calling of __alloc_pages() in __kmalloc_section_memmap(). It can reduce noisy failure message. In ia64, section size is 1 GB, this means that order 8 pages are necessary for each section's memmap. It is often very hard requirement under heavy memory pressure as you know. So, __alloc_pages() gives up allocation and shows many noisy stack traces which means no page for each sections. (Current my environment shows 32 times of stack trace....) But, __kmalloc_section_memmap() calls vmalloc() after failure of it, and it can succeed allocation of memmap. So, its stack trace warning becomes just noisy. I suppose it shouldn't be shown. Signed-off-by: Yasunori Goto <y-goto@jp.fujitsu.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions