The patch titled Subject: mem-hotplug: improve zone_movable_is_highmem logic has been removed from the -mm tree. Its filename was mem-hotplug-improve-zone_movable_is_highmem-logic.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Wang Nan <wangnan0@xxxxxxxxxx> Subject: mem-hotplug: improve zone_movable_is_highmem logic In original code, zone_movable_is_highmem() assumes ZONE_MOVABLE not highmem if CONFIG_HAVE_MEMBLOCK_NODE_MAP is not set. In online_pages, it extracts pages from the previous zone before ZONE_MOVABLE. Which is logically inconsistent: If HAVE_MEMBLOCK_NODE_MAP is turned off but HIGHMEM is on, zone_movable_is_highmem() makes movable zone not highmem, but online_pages() extracts pages from ZONE_HIGHMEM. This inconsistency doesn't cause real problem currently, because all architectures support online_pages also have HAVE_MEMBLOCK_NODE_MAP. However, fixing it makes code clear, and also helps futher coding. Signed-off-by: Wang Nan <wangnan0@xxxxxxxxxx> Cc: Zhang Zhen <zhangzhen@xxxxxxxxxx> Cc: Mel Gorman <mgorman@xxxxxxx> Cc: Jiang Liu <liuj97@xxxxxxxxx> Cc: Li Zefan <lizefan@xxxxxxxxxx> Cc: Yinghai Lu <yinghai@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- include/linux/mmzone.h | 2 ++ 1 file changed, 2 insertions(+) diff -puN include/linux/mmzone.h~mem-hotplug-improve-zone_movable_is_highmem-logic include/linux/mmzone.h --- a/include/linux/mmzone.h~mem-hotplug-improve-zone_movable_is_highmem-logic +++ a/include/linux/mmzone.h @@ -872,6 +872,8 @@ static inline int zone_movable_is_highme { #if defined(CONFIG_HIGHMEM) && defined(CONFIG_HAVE_MEMBLOCK_NODE_MAP) return movable_zone == ZONE_HIGHMEM; +#elif defined(CONFIG_HIGHMEM) + return (ZONE_MOVABLE - 1) == ZONE_HIGHMEM; #else return 0; #endif _ Patches currently in -mm which might be from wangnan0@xxxxxxxxxx are origin.patch -- 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