Lines Matching refs:page

9 The main intend of page migration is to reduce the latency of memory access
22 which provides an interface similar to other numa functionality for page
25 proc(5) man page.
31 manual page migration support. Automatic page migration may be implemented
67    Calling isolate_lru_page increases the references to the page
68    so that it cannot vanish while the page migration occurs.
70    the page.
74    how to allocate the correct new page given the old page.
78    the new page for each page that is considered for
84 migrate_pages() does several passes over its list of pages. A page is moved
85 if all references to a page are removable at the time. The page has
87 is increased so that the page cannot be freed while page migration occurs.
91 1. Lock the page to be migrated
95 3. Prep the new page that we want to move to. It is locked
97    page immediately lock while the move is in progress.
99 4. The new page is prepped with some settings from the old page so that
100    accesses to the new page will discover a page with the correct settings.
102 5. All the page table references to the page are converted
104    This decrease the mapcount of a page. If the resulting
105    mapcount is not zero then we do not migrate the page.
106    All user space processes that attempt to access the page
107    will now wait on the page lock.
110    to access the page via the mapping to block on the radix tree spinlock.
112 7. The refcount of the page is examined and we back out if references remain
113    otherwise we know that we are the only one referencing this page.
116    page then we back out because someone else modified the radix tree.
118 9. The radix tree is changed to point to the new page.
120 10. The reference count of the old page is dropped because the radix tree
121     reference is gone. A reference to the new page is established because
122     the new page is referenced to by the radix tree.
126     to sleeping on the locked new page.
128 12. The page contents are copied to the new page.
130 13. The remaining page flags are copied to the new page.
132 14. The old page flags are cleared to indicate that the page does
135 15. Queued up writeback on the new page is triggered.
137 16. If migration entries were page then replace them with real ptes. Doing
139     the page lock.
141 19. The page locks are dropped from the old and new page.
142     Processes waiting on the page lock will redo their page faults
143     and will reach the new page.
145 20. The new page is moved to the LRU and can be scanned by the swapper