Lines Matching full:mmu
2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
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
30 shared across fork() or clone() without CLONE_VM in the MMU case. Since
31 the no-MMU case doesn't support these, behaviour is identical to
36 In the MMU case: VM regions backed by pages read from file; changes to
39 In the no-MMU case:
56 are visible in other processes (no MMU protection), but should not
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
85 as for the MMU case. If the filesystem does not provide any such
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
108 Further notes on no-MMU MMAP
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
148 visible through /proc/maps in no-MMU mode.
151 /proc/<pid>/maps in no-MMU mode.
180 No-MMU mremap