mm-memory_hotplug-document-why-shuffle_zone-is-relevant.patch removed from -mm tree
The patch titled
Subject: mm/memory_hotplug: document why shuffle_zone() is relevant
has been removed from the -mm tree. Its filename was
mm-memory_hotplug-document-why-shuffle_zone-is-relevant.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: David Hildenbrand <[email protected]>
Subject: 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.
---
mm/memory_hotplug.c | 8 ++++++++ 1 file changed, 8 insertions(+)
mm/memory_hotplug.c renamed from mm/memory_hotplug.c~mm-memory_hotplug-document-why-shuffle_zone-is-relevant +8 -0
@@ -831,6 +831,14 @@ int __ref online_pages(unsigned long pfn zone->zone_pgdat->node_present_pages += onlined_pages;pgdat_resize_unlock (zone->zone_pgdat, &flags); +/* +* When exposing larger, physically contiguous memory areas to the +* buddy, shuffling in the buddy (when freeing onlined pages, putting +* them either to the head or the tail of the freelist) is only helpful +* for maintaining the shuffle, but not for creating the initial +* shuffle. Shuffle the whole zone to make sure the just onlined pages +* are properly distributed across the whole freelist. +*/ shuffle_zone (zone);node_states_set_node (nid, &arg);
_
Patches currently in -mm which might be from [email protected] are