Documentation/mm/page_migration.rst

5 Page migration allows moving the physical location of pages between
8 system rearranges the physical location of those pages.
10 Also see Documentation/mm/hmm.rst for migrating pages to or from device
14 by moving pages near to the processor where the process accessing that memory
18 pages are located through the MF_MOVE and MF_MOVE_ALL options while setting
19 a new memory policy via mbind(). The pages of a process can also be relocated
21 migrate_pages() function call takes two sets of nodes and moves pages of a
28 pages of a process are located. See also the numa_maps documentation in the
33 administrator may detect the situation and move the pages of the process
36 through user space processes that move pages. A special function call
37 "move_pages" allows the moving of individual pages within a process.
39 accesses and may use the result to move pages to more advantageous
44 move pages when a task is moved to another cpuset (See
47 a new cpuset then also all its pages are moved with it so that the
48 performance of the process does not sink dramatically. Also the pages
52 Page migration allows the preservation of the relative location of pages
66 1. Remove pages from the LRU.
68    Lists of pages to be migrated are generated by scanning over
69    pages and moving them into lists. This is done by
87 migrate_pages() does several passes over its list of pages. A page is moved
154 pages.  For compaction purposes, it is also useful to be able to move
155 non-LRU pages, such as zsmalloc and virtio-balloon pages.
157 If a driver wants to make its pages movable, it should define a struct
171    For example, migration of a single 2MB THP that has 4KB-size base pages
183    to be split. After splitting, a migration retry was used for its sub-pages.