There's no good reason to disallow the migration of pages shared by multiple processes - the migration code itself is already properly walking the rmap chain. So allow it. We've tested this with various workloads and no ill effect appears to have come from this. Cc: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> Cc: Andrea Arcangeli <aarcange@xxxxxxxxxx> Cc: Rik van Riel <riel@xxxxxxxxxx> Cc: Mel Gorman <mgorman@xxxxxxx> Signed-off-by: Ingo Molnar <mingo@xxxxxxxxxx> --- mm/migrate.c | 6 ------ 1 file changed, 6 deletions(-) diff --git a/mm/migrate.c b/mm/migrate.c index 72d1056..b89062d 100644 --- a/mm/migrate.c +++ b/mm/migrate.c @@ -1427,12 +1427,6 @@ int migrate_misplaced_page(struct page *page, int node) gfp_t gfp = GFP_HIGHUSER_MOVABLE; /* - * Don't migrate pages that are mapped in multiple processes. - */ - if (page_mapcount(page) != 1) - goto out; - - /* * Never wait for allocations just to migrate on fault, but don't dip * into reserves. And, only accept pages from the specified node. No * sense migrating to a different "misplaced" page! -- 1.7.11.7 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>