mm-page_alloc-avoid-merging-non-fallbackable-pageblocks-with-others.patch removed from -mm tree
The patch titled
Subject: mm: page_alloc: avoid merging non-fallbackable pageblocks with others
has been removed from the -mm tree. Its filename was
mm-page_alloc-avoid-merging-non-fallbackable-pageblocks-with-others.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Zi Yan <[email protected]>
Subject: mm: page_alloc: avoid merging non-fallbackable pageblocks with others
This is done in addition to MIGRATE_ISOLATE pageblock merge avoidance. It prepares for the upcoming removal of the MAX_ORDER-1 alignment requirement for CMA and alloc_contig_range().
MIGRATE_HIGHATOMIC should not merge with other migratetypes like MIGRATE_ISOLATE and MIGRARTE_CMA[1], so this commit prevents that too.
Remove MIGRATE_CMA and MIGRATE_ISOLATE from fallbacks list, since they are never used.
[1] https://lore.kernel.org/linux-mm/[email protected]/
---
include/linux/mmzone.h | 11 +++++++++ mm/page_alloc.c | 46 ++++++++++++++++++--------------------- 2 files changed, 33 insertions(+), 24 deletions(-)
include/linux/mmzone.h renamed from include/linux/mmzone.h~mm-page_alloc-avoid-merging-non-fallbackable-pageblocks-with-others +11 -0
@@ -83,6 +83,17 @@ static inline bool is_migrate_movable(inreturn is_migrate_cma (mt) || mt ==MIGRATE_MOVABLE ; } +/* +* Check whether a migratetype can be merged with another migratetype. +* +* It is only mergeable when it can fall back to other migratetypes for +* allocation. See fallbacks[MIGRATE_TYPES][3] in page_alloc.c. +*/ +static inline bool migratetype_is_mergeable (int mt) +{ +return mt <MIGRATE_PCPTYPES ; +} +#define for_each_migratetype_order (order, type) \ for (order = 0; order < MAX_ORDER; order++) \ for (type = 0; type < MIGRATE_TYPES; type++)
mm/page_alloc.c renamed from mm/page_alloc.c~mm-page_alloc-avoid-merging-non-fallbackable-pageblocks-with-others +22 -24
80 lines not on this page · raw message
_
Patches currently in -mm which might be from [email protected] are