Lines Matching refs:page
120 * Determine whether the given page should be returned,
121 * based on the page's state and on the given return policy.
123 * We should return the page if one of the following is true:
158 * given page. See the description of
163 * completed, blocked, or that the page must
174 "m_o_lock_page, page 0x%X rtn %d flush %d prot %d\n",
178 * If we cannot change access to the page,
180 * (busy page) or because a mapping has been
194 /* dump the page, pager wants us to */
209 * If the page is wired, just clean or return the page if needed.
225 * If the page is to be flushed, allow
233 * Set the page lock.
247 * Handle page returning.
253 * to flush the page anyway,
255 * page from the pageout
332 * memory object. For each page in the given range,
334 * 1) restrict access to the page (disallow
337 * is RETURN_DIRTY and the page is dirty, or
338 * "should_return" is RETURN_ALL and the page
344 * same page alignment as the starting offset are
461 * same as memory_object_lock_request but page protection
608 * Mark the page busy since we will unlock the
640 /* let's no flush a wired page... */
717 * XXX NOTE: May want to consider converting this to a page list
764 vm_page_t page;
824 &page,
834 page->object, top_page);
839 if (!page->active && !page->inactive)
840 vm_page_deactivate(page);
843 PAGE_WAKEUP_DONE(page);
904 * to use the resident page list to drive our checks
906 * the page which means the resident queue can change which
910 * flush to disk... the resident page queue is NOT ordered.
914 * the resident page queue (if it's small enough) and develop
918 * worst case (a single resident page at the end of an extremely large
945 * this is a page we're interested in
953 * we're at the last page of the space
965 * this page
981 * on the min and max page offsets
1004 * page that forced us to abandon trying
1815 /* Allow manipulation of individual page state. This is actually part of */
1837 * memory_object_page_op for page_op functions which do not require page
1839 * a low-cost alternative to page manipulation via UPLs when only a single
1840 * page was involved. The range_op call establishes the ability in the _op
1841 * family of functions to work on multiple pages where the lack of page level