Lines Matching +full:use +full:- +full:guard +full:- +full:pages

4 .\" Redistribution and use in source and binary forms, with or without
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
43 system call causes the pages starting at
55 Any such extension beyond the end of the mapped object will be zero-filled.
85 is non-zero, it is used as a hint to the system.
102 .Bl -tag -width PROT_WRITE -compact
104 Pages may not be accessed.
106 Pages may be read.
108 Pages may be written.
110 Pages may be executed.
139 .Bl -tag -width MAP_PREFAULT_READ
154 Align the region to maximize the potential use of large
156 pages.
165 the physical address of existing pages of a file may require a specific
172 must be \-1.
177 .\"Mapped from a regular file or character-special device memory.
204 pages in the range from
215 Instead of a mapping, create a guard of the specified size.
220 will not create mappings in the address range of a guard unless
234 Typically this prevents the update daemons from flushing pages dirtied
236 unassociated processes using a file-backed shared memory map.
238 this option any VM pages you dirty may be flushed to disk every so often
239 (every 30-60 seconds usually) which can create performance problems if you
240 do not need that to occur (such as when you are using shared file-backed
245 maintained whether you use
260 In order to avoid such fragmentation you should always pre-allocate the
267 pages, because pages may be flushed to disk in a totally random order.
271 to implement a file-based shared memory store.
298 used to associate dirty VM pages with file system buffers and thus cause
301 Immediately update the calling process's lowest-level virtual address
319 adjoining guard that both reserves address space for the mapped region
321 Together, the mapped region and the guard occupy
324 The guard starts at the returned address, and the mapped region ends at
328 Upon access to the guard, the mapped region automatically grows in size,
329 and the guard shrinks by an equal amount.
330 Essentially, the boundary between the guard and the mapped region moves
332 However, the guard will never shrink to less than the number of pages
348 must be -1 and
354 The size of the guard, in pages, is specified by sysctl
360 system call does not unmap pages, see
367 argument, a portable program must only use page-aligned values.
369 Large page mappings require that the pages backing an object be
371 The system will automatically attempt to use large page mappings when
372 mapping an object that is already backed by large pages in RAM by
374 alignment of the large physical pages.
375 The system may also use large page mappings when mapping portions of an
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.
401 .Bl -tag -width Er
460 is less than or equal to the guard size.
487 argument was not -1.
510 argument was not -1, or the