Lines Matching full:pages
43 system call causes the pages starting at
104 Pages may not be accessed.
106 Pages may be read.
108 Pages may be written.
110 Pages may be executed.
156 pages.
165 the physical address of existing pages of a file may require a specific
204 pages in the range from
234 Typically this prevents the update daemons from flushing pages dirtied
238 this option any VM pages you dirty may be flushed to disk every so often
267 pages, because pages may be flushed to disk in a totally random order.
298 used to associate dirty VM pages with file system buffers and thus cause
332 However, the guard will never shrink to less than the number of pages
354 The size of the guard, in pages, is specified by sysctl
360 system call does not unmap pages, see
369 Large page mappings require that the pages backing an object be
372 mapping an object that is already backed by large pages in RAM by
374 alignment of the large physical pages.
376 object that are not yet backed by pages in RAM.
383 uses large pages so that the mapping will be consistent with the existing
384 large pages.
385 This flag is mostly useful for maximizing the use of large pages on the
386 first mapping of objects that do not yet have pages present in RAM.