Lines Matching full:pages

7 Page migration allows the moving of the physical location of pages between
10 system rearranges the physical location of those pages.
13 by moving pages near to the processor where the process accessing that memory
17 pages are located through the MF_MOVE and MF_MOVE_ALL options while setting
18 a new memory policy via mbind(). The pages of process can also be relocated
20 migrate_pages function call takes two sets of nodes and moves pages of a
27 pages of a process are located. See also the numa_maps documentation in the
32 administrator may detect the situation and move the pages of the process
35 through user space processes that move pages. A special function call
36 "move_pages" allows the moving of individual pages within a process.
38 accesses and may use the result to move pages to more advantageous
43 move pages when a task is moved to another cpuset (See
46 a new cpuset then also all its pages are moved with it so that the
47 performance of the process does not sink dramatically. Also the pages
51 Page migration allows the preservation of the relative location of pages
65 1. Remove pages from the LRU.
67    Lists of pages to be migrated are generated by scanning over
68    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
155 *LRU* pages. However, there are potential non-lru pages which can be migrated
156 in drivers, for example, zsmalloc, virtio-balloon pages.
158 For virtio-balloon pages, some parts of migration code path have been hooked
160 It's too specific to a driver so other drivers who want to make their pages
164 generic functions for non-LRU movable pages without driver specific hooks
167 If a driver want to make own pages movable, it should define three functions
233      LRU pages never can have PAGE_MAPPING_MOVABLE in page->mapping. It is also
234      good for just peeking to test non-lru movable pages before more expensive