Lines Matching full:pages

7 Page migration allows moving the physical location of pages between
10 system rearranges the physical location of those pages.
13 for migrating pages to or from device private memory.
16 by moving pages near to the processor where the process accessing that memory
20 pages are located through the MF_MOVE and MF_MOVE_ALL options while setting
21 a new memory policy via mbind(). The pages of a process can also be relocated
23 migrate_pages() function call takes two sets of nodes and moves pages of a
30 pages of a process are located. See also the numa_maps documentation in the
35 administrator may detect the situation and move the pages of the process
38 through user space processes that move pages. A special function call
39 "move_pages" allows the moving of individual pages within a process.
41 accesses and may use the result to move pages to more advantageous
46 move pages when a task is moved to another cpuset (See
49 a new cpuset then also all its pages are moved with it so that the
50 performance of the process does not sink dramatically. Also the pages
54 Page migration allows the preservation of the relative location of pages
68 1. Remove pages from the LRU.
70    Lists of pages to be migrated are generated by scanning over
71    pages and moving them into lists. This is done by
90 migrate_pages() does several passes over its list of pages. A page is moved
156 for NUMA, compaction also uses migration to create high-order pages.
159 *LRU* pages. However, there are potential non-LRU pages which can be migrated
160 in drivers, for example, zsmalloc, virtio-balloon pages.
162 For virtio-balloon pages, some parts of migration code path have been hooked
164 It's too specific to a driver so other drivers who want to make their pages
168 generic functions for non-LRU movable pages without driver specific hooks
171 If a driver wants to make its pages movable, it should define three functions
230      For testing of non-LRU movable pages, VM supports __PageMovable() function.
231      However, it doesn't guarantee to identify non-LRU movable pages because
237      pages can never have PAGE_MAPPING_MOVABLE set in page->mapping. It is also
238      good for just peeking to test non-LRU movable pages before more expensive
269    has 4KB-size base pages (subpages) will cause this counter to increase by
281    to be split. After splitting, a migration retry was used for it's sub-pages.