[PATCH] memory hotplug locking: node_size_lock
pgdat->node_size_lock is basically only neeeded in one place in the normal code: show_mem(), which is the arch-specific sysrq-m printing function. Strictly speaking, the architectures not doing memory hotplug do no need this locking in show_mem(). However, they are all included for completeness. This should also make any future consolidation of all of the implementations a little more straightforward. This lock is also held in the sparsemem code during a memory removal, as sections are invalidated. This is the place there pfn_valid() is made false for a memory area that's being removed. The lock is only required when doing pfn_valid() operations on memory which the user does not already have a reference on the page, such as in show_mem(). Signed-off-by:Dave Hansen <haveblue@us.ibm.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
Showing
- arch/alpha/mm/numa.c 3 additions, 0 deletionsarch/alpha/mm/numa.c
- arch/i386/mm/pgtable.c 3 additions, 0 deletionsarch/i386/mm/pgtable.c
- arch/ia64/mm/discontig.c 6 additions, 1 deletionarch/ia64/mm/discontig.c
- arch/m32r/mm/init.c 8 additions, 1 deletionarch/m32r/mm/init.c
- arch/parisc/mm/init.c 3 additions, 0 deletionsarch/parisc/mm/init.c
- arch/ppc64/mm/init.c 6 additions, 0 deletionsarch/ppc64/mm/init.c
- include/linux/memory_hotplug.h 34 additions, 0 deletionsinclude/linux/memory_hotplug.h
- include/linux/mmzone.h 12 additions, 0 deletionsinclude/linux/mmzone.h
- mm/page_alloc.c 1 addition, 0 deletionsmm/page_alloc.c
Loading
Please register or sign in to comment