summaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorBaoquan He <bhe@redhat.com>2020-04-02 07:09:34 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2020-04-02 19:35:30 +0300
commit4027149abde8d57da4c4c4f498b310c85a297bba (patch)
tree259943310ec8c46f0baaf9adc5a452a87967b6e0 /init
parent3af776f601dc13e1cae1f0f461407533669cf666 (diff)
downloadlinux-4027149abde8d57da4c4c4f498b310c85a297bba.tar.xz
mm/sparse.c: allocate memmap preferring the given node
When allocating memmap for hot added memory with the classic sparse, the specified 'nid' is ignored in populate_section_memmap(). While in allocating memmap for the classic sparse during boot, the node given by 'nid' is preferred. And VMEMMAP prefers the node of 'nid' in both boot stage and memory hot adding. So seems no reason to not respect the node of 'nid' for the classic sparse when hot adding memory. Use kvmalloc_node instead to use the passed in 'nid'. Signed-off-by: Baoquan He <bhe@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org> Reviewed-by: David Hildenbrand <david@redhat.com> Reviewed-by: Wei Yang <richard.weiyang@gmail.com> Acked-by: Michal Hocko <mhocko@suse.com> Acked-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com> Link: http://lkml.kernel.org/r/20200316125625.GH3486@MiWiFi-R3L-srv Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions