diff options
author | Dave Hansen <haveblue@us.ibm.com> | 2005-10-30 02:16:52 +0100 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-10-30 05:40:44 +0100 |
commit | 208d54e5513c0c02d85af0990901354c74364d5c (patch) | |
tree | 83922f1d4a83f19bffcbff299044f421bd7e9c73 /mm/highmem.c | |
parent | [PATCH] memory hotplug prep: fixup bad_range() (diff) | |
download | linux-208d54e5513c0c02d85af0990901354c74364d5c.tar.xz linux-208d54e5513c0c02d85af0990901354c74364d5c.zip |
[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>
Diffstat (limited to 'mm/highmem.c')
0 files changed, 0 insertions, 0 deletions