Lines Matching refs:pages

8 pages that the kernel's pageframe replacement algorithm (PFRA) would like
36 Thus, as its name implies, cleancache is not suitable for dirty pages.
37 Cleancache has complete discretion over what pages to preserve and what
38 pages to discard and when.
48 an "invalidate_inode" will invalidate all pages associated with the specified
50 all pages in all files specified by the given pool id and also surrender
58 same UUID will receive the same pool id, thus allowing the pages to
102 effectiveness of the pagecache.  Clean pagecache pages are
104 addressable to the kernel); fetching those pages later avoids "refaults"
113 balancing for some RAM-like devices).  Evicted page-cache pages (and
114 swap pages) are a great use for this kind of slower-than-RAM-but-much-
117 write -- and indirectly "name" -- the pages.
128 virtual machines, but the pages can be compressed and deduplicated to
130 underutilized RAM (e.g. with "self-ballooning"), page cache pages
131 are the first to go, and cleancache allows those pages to be
136 device that stores pages of data in a compressed state.  And
230 - To maximize performance, all pages fetched from the FS should
243 won't work because cleancache retains pagecache data pages
249 invalidated the pages when the inode kva was freed, much of the value
250 of cleancache would be lost because the cache of pages in cleanache
252 useful if the pages survive inode cache removal.