Lines Matching refs:may
82 (such as ramfs or tmpfs) may choose to honour an open, truncate, mmap
101 In the no-MMU case: The character device driver may choose to honour
112 (*) A request for a private mapping of a file may return a buffer that is not
113 page-aligned. This is because XIP may take place, and the data may not be
118 of the space may be wasted as the kernel must allocate a power-of-2
187 The mremap() function is partially supported. It may change the size of a
188 mapping, and may move it[*] if MREMAP_MAYMOVE is specified and if the new size
195 Shared mappings may not be moved. Shareable mappings may not be moved either,
199 a previously mapped object. It may not be used to create holes in existing
212 to get a proposed address for the mapping. This may return an error if it
240 Some types of device may present a different appearance to anyone
248 mappings may still be mapped directly off the device under some