[PATCH 4/4] mm: remove direct calling of migration
From: Gioh Kim <hidden>
Date: 2015-07-13 08:35:19
Also in:
dri-devel, linux-fsdevel, linux-mm, lkml
Subsystem:
memory management, memory management - memory policy and migration, the rest · Maintainers:
Andrew Morton, David Hildenbrand, Linus Torvalds
From: Gioh Kim <redacted> Migration is completely generalized so that migrating mobile page is processed with lru-pages in move_to_new_page. Signed-off-by: Gioh Kim <redacted> Acked-by: Rafael Aquini <redacted> --- mm/migrate.c | 15 --------------- 1 file changed, 15 deletions(-)
diff --git a/mm/migrate.c b/mm/migrate.c
index 53f0081d..e6644ac 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c@@ -844,21 +844,6 @@ static int __unmap_and_move(struct page *page, struct page *newpage, } } - if (unlikely(mobile_page(page))) { - /* - * A mobile page does not need any special attention from - * physical to virtual reverse mapping procedures. - * Skip any attempt to unmap PTEs or to remap swap cache, - * in order to avoid burning cycles at rmap level, and perform - * the page migration right away (proteced by page lock). - */ - lock_page(newpage); - rc = page->mapping->a_ops->migratepage(page->mapping, - newpage, page, mode); - unlock_page(newpage); - goto out_unlock; - } - /* * Corner case handling: * 1. When a new swap-cache page is read into, it is added to the LRU
--
2.1.4