3 4Page migration allows the moving of the physical location of pages between
5nodes in a numa system while the process is running. This means that the
6virtual addresses that the process sees do not change. However, the
7system rearranges the physical location of those pages.
8 9The main intend of page migration is to reduce the latency of memory access
10by moving pages near to the processor where the process accessing that memory
12 13Page migration allows a process to manually relocate the node on which its
14pages are located through the MF_MOVE and MF_MOVE_ALL options while setting
15a new memory policy via mbind(). The pages of process can also be relocated
16from another process using the sys_migrate_pages() function call. The
17migrate_pages function call takes two sets of nodes and moves pages of a
18process that are located on the from nodes to the destination nodes.
19Page migration functions are provided by the numactl package by Andi Kleen
20(a version later than 0.9.3 is required. Get it from
21ftp://oss.sgi.com/www/projects/libnuma/download/). numactl provides libnuma
22which provides an interface similar to other numa functionality for page
23migration. cat /proc/<pid>/numa_maps allows an easy review of where the
24pages of a process are located. See also the numa_maps documentation in the
25proc(5) man page.
26 27Manual migration is useful if for example the scheduler has relocated
28a process to a processor on a distant node. A batch scheduler or an
29administrator may detect the situation and move the pages of the process
30nearer to the new processor. The kernel itself does only provide
31manual page migration support. Automatic page migration may be implemented
32through user space processes that move pages. A special function call
33"move_pages" allows the moving of individual pages within a process.
34A NUMA profiler may f.e. obtain a log showing frequent off node
35accesses and may use the result to move pages to more advantageous
37 38Larger installations usually partition the system using cpusets into
39sections of nodes. Paul Jackson has equipped cpusets with the ability to
40move pages when a task is moved to another cpuset (See
42Cpusets allows the automation of process locality. If a task is moved to
43a new cpuset then also all its pages are moved with it so that the
44performance of the process does not sink dramatically. Also the pages
45of processes in a cpuset are moved if the allowed memory nodes of a
46cpuset are changed.
47 48Page migration allows the preservation of the relative location of pages
49within a group of nodes for all migration techniques which will preserve a
50particular memory allocation pattern generated even after migrating a
51process. This is necessary in order to preserve the memory latencies.
52Processes will run with similar performance after migration.
53 54Page migration occurs in several steps. First a high level
55description for those trying to use migrate_pages() from the kernel
56(for userspace usage see the Andi Kleen's numactl package mentioned above)
57and then a low level description of how the low level details work.
58 59A. In kernel use of migrate_pages()
61 621. Remove pages from the LRU.
63 64 Lists of pages to be migrated are generated by scanning over
65 pages and moving them into lists. This is done by
66 calling isolate_lru_page().
67 Calling isolate_lru_page increases the references to the page
68 so that it cannot vanish while the page migration occurs.
69 It also prevents the swapper or other scans to encounter
70 the page.
71 722. We need to have a function of type new_page_t that can be
73 passed to migrate_pages(). This function should figure out
74 how to allocate the correct new page given the old page.
75 763. The migrate_pages() function is called which attempts
77 to do the migration. It will call the function to allocate
78 the new page for each page that is considered for
80 81B. How migrate_pages() works
83 84migrate_pages() does several passes over its list of pages. A page is moved
85if all references to a page are removable at the time. The page has
86already been removed from the LRU via isolate_lru_page() and the refcount
87is increased so that the page t cannobe frl8dtion#L87" id="L87cref="Documentati87c
"Doccriginst LXR nnftw"Doce by Ann/vm/pagehtprojesourcehtiatinetnload/). nuxe">LXR aommunity all,s iiseex eniratiol.9.3 is re bn/vm/pageaailto:email@example.com">firstname.lastname@example.org all.
div i0"> 5sub bn/vm/pageaaiitysub bn/vm/pageaaiitysub bn/vm/pageaaii 79 movin#Lly hosid="L65LXR aommunity alwww." ip1" -/a>tion/vm/R ip1" La>tio ASilto:uration#rtcreLa> 79" c="li0nigratopemem1ryocumrvilasssim/pa1995. nnftw"Doc/bodyeaa/htmlLXR