Documentation/mm/page_migration.rst

6 nodes in a NUMA system while the process is running. This means that the
7 virtual addresses that the process sees do not change. However, the
14 by moving pages near to the processor where the process accessing that memory
17 Page migration allows a process to manually relocate the node on which its
19 a new memory policy via mbind(). The pages of a process can also be relocated
20 from another process using the sys_migrate_pages() function call. The
22 process that are located on the from nodes to the destination nodes.
28 pages of a process are located. See also the numa_maps documentation in the
32 a process to a processor on a distant node. A batch scheduler or an
33 administrator may detect the situation and move the pages of the process
37 "move_pages" allows the moving of individual pages within a process.
46 Cpusets allow the automation of process locality. If a task is moved to
48 performance of the process does not sink dramatically. Also the pages
55 process. This is necessary in order to preserve the memory latencies.