summaryrefslogtreecommitdiffstats
path: root/mm/shuffle.c
diff options
context:
space:
mode:
authorDavid Hildenbrand <david@redhat.com>2020-08-06 23:25:35 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2020-08-07 11:33:29 -0700
commit93146d98ce73fa416be3ffa147247a2454645ebc (patch)
tree5db7cd290cc48ebcb4b1c175538324386704f74e /mm/shuffle.c
parent56b9413bcb369f1329a438c7b61d235b4123e794 (diff)
downloadlinux-stable-93146d98ce73fa416be3ffa147247a2454645ebc.tar.gz
linux-stable-93146d98ce73fa416be3ffa147247a2454645ebc.tar.bz2
linux-stable-93146d98ce73fa416be3ffa147247a2454645ebc.zip
mm/memory_hotplug: document why shuffle_zone() is relevant
It's not completely obvious why we have to shuffle the complete zone - introduced in commit e900a918b098 ("mm: shuffle initial free memory to improve memory-side-cache utilization") - because some sort of shuffling is already performed when onlining pages via __free_one_page(), placing MAX_ORDER-1 pages either to the head or the tail of the freelist. Let's document why we have to shuffle the complete zone when exposing larger, contiguous physical memory areas to the buddy. Signed-off-by: David Hildenbrand <david@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Acked-by: Dan Williams <dan.j.williams@intel.com> Acked-by: Michal Hocko <mhocko@suse.com> Cc: Alexander Duyck <alexander.h.duyck@linux.intel.com> Cc: Dan Williams <dan.j.williams@intel.com> Cc: Michal Hocko <mhocko@suse.com> Link: http://lkml.kernel.org/r/20200624094741.9918-3-david@redhat.com Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/shuffle.c')
0 files changed, 0 insertions, 0 deletions