Lines Matching refs:In
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
36 In the MMU case: VM regions backed by pages read from file; changes to
39 In the no-MMU case:
61 In the MMU case: like the non-PROT_WRITE case, except that the pages in
66 In the no-MMU case: works much like the non-PROT_WRITE case, except
71 In the MMU case: VM regions backed by pages read from file; changes to
75 In the no-MMU case: not supported.
79 In the MMU case: As for ordinary regular files.
81 In the no-MMU case: The filesystem providing the memory-backed file
83 sequence by providing a contiguous sequence of pages to map. In that
90 In the MMU case: As for ordinary regular files.
92 In the no-MMU case: As for memory backed regular files, but the
99 In the MMU case: As for ordinary regular files.
101 In the no-MMU case: The character device driver may choose to honour
125 In the MMU case this can be achieved with reasonable performance as
133 In the no-MMU case, however, anonymous mappings are backed by physical
240 In such a case, care must be taken lest userspace see a shared or a
279 allocator. In order to retain finer-grained control over fragmentation, this