The patch titled
Subject: mm: memory hot-add: memory can not been added to movable zone
has been removed from the -mm tree. Its filename was
memory-hot-addedthe-memory-can-not-been-added-to-movable-zone.patch
This patch was dropped because it was nacked
------------------------------------------------------
From: Changsheng Liu <liuchangcheng@xxxxxxxxxx>
Subject: mm: memory hot-add: memory can not been added to movable zone
When memory is hot added, should_add_memory_movable() always returns 0
because the movable zone is empty, so the memory that was hot added will
add to the normal zone even if we want to remove the memory.
So we change should_add_memory_movable(): if CONFIG_MOVABLE_NODE=y it will
return 1 when the movable zone is empty.
[akpm@xxxxxxxxxxxxxxxxxxxx: cleanup]
Signed-off-by: Changsheng Liu <liuchangcheng@xxxxxxxxxx>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@xxxxxxxxxxxxxx>
Cc: Vlastimil Babka <vbabka@xxxxxxx>
Cc: Tang Chen <tangchen@xxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memory_hotplug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/memory_hotplug.c~memory-hot-addedthe-memory-can-not-been-added-to-movable-zone mm/memory_hotplug.c
--- a/mm/memory_hotplug.c~memory-hot-addedthe-memory-can-not-been-added-to-movable-zone
+++ a/mm/memory_hotplug.c
@@ -1207,7 +1207,7 @@ static int should_add_memory_movable(int
struct zone *movable_zone = pgdat->node_zones + ZONE_MOVABLE;
if (zone_is_empty(movable_zone))
- return 0;
+ return IS_ENABLED(CONFIG_MOVABLE_NODE);
if (movable_zone->zone_start_pfn <= start_pfn)
return 1;
_
Patches currently in -mm which might be from liuchangcheng@xxxxxxxxxx are
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
