Lines Matching refs:memory

5 The kernel has limited support for memory mapping under no-MMU conditions, such
6 as are used in uClinux environments. From the userspace point of view, memory
53            memory and any extraneous space beyond the EOF will be cleared
81 	In the no-MMU case: The filesystem providing the memory-backed file
84 	case, a shared-writable memory mapping will be possible. It will work
92 	In the no-MMU case: As for memory backed regular files, but the
95 	all its memory as a contiguous array upfront.
103 	provides memory or quasi-memory that can be accessed directly. Examples
122  (*) The memory allocated by a request for an anonymous mapping will normally
139      However, for memory that isn't required to be precleared - such as that
141      indicate to the kernel that it shouldn't bother clearing the memory before
158      driver or filesystem so that the contents can be read into the memory
168 Both SYSV IPC SHM shared memory and POSIX shared memory is supported in NOMMU
190 memory to which the mapping refers, or if a smaller slab object could be used.
256 Provision of shared mappings on memory backed files is similar to the provision
264 memory.
276 should allocate sufficient contiguous memory to honour any supported mapping.
284 when performing an allocation.  This can have adverse effects on memory