The patch titled
Subject: mm: use migrate_prep() instead of migrate_prep_local()
has been removed from the -mm tree. Its filename was
mm-use-migrate_prep-instead-of-migrate_prep_local.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
Subject: mm: use migrate_prep() instead of migrate_prep_local()
__alloc_contig_migrate_range() should use all possible ways to get all the
pages migrated from the given memory range, so pruning per-cpu lru lists
for all CPUs is required, regadless the cost of such operation. Otherwise
some pages which got stuck at per-cpu lru list might get missed by
migration procedure causing the contiguous allocation to fail.
Reported-by: SeongHwan Yoon <sunghwan.yun@xxxxxxxxxxx>
Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
Signed-off-by: Kyungmin Park <kyungmin.park@xxxxxxxxxxx>
Acked-by: Michal Nazarewicz <mina86@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/page_alloc.c~mm-use-migrate_prep-instead-of-migrate_prep_local mm/page_alloc.c
--- a/mm/page_alloc.c~mm-use-migrate_prep-instead-of-migrate_prep_local
+++ a/mm/page_alloc.c
@@ -5727,7 +5727,7 @@ static int __alloc_contig_migrate_range(
unsigned int tries = 0;
int ret = 0;
- migrate_prep_local();
+ migrate_prep();
while (pfn < end || !list_empty(&cc->migratepages)) {
if (fatal_signal_pending(current)) {
_
Patches currently in -mm which might be from m.szyprowski@xxxxxxxxxxx are
origin.patch
linux-next.patch
mm-cma-warn-if-freed-memory-is-still-in-use.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
