Lines Matching full:mapping

70 of mapping function calls into the filesystem across a larger amount of
78    1. Obtain a space mapping via ``->iomap_begin``
82       1. Revalidate the mapping and go back to (1) above, if necessary.
89    4. Release the mapping via ``->iomap_end``, if necessary
130  * **filesystem mapping lock**: This synchronization primitive is
131    internal to the filesystem and must protect the file mapping data
132    from updates while a mapping is being sampled.
138    mapping.
154 The filesystem communicates to the iomap iterator the mapping of
176    bytes, covered by this mapping.
179  * ``type`` describes the type of the space mapping:
184      the mapping.
204      Reads from this type of mapping will return zeroes to the caller.
206      mapping to MAPPED.
215  * ``flags`` describe the status of the space mapping.
218    * **IOMAP_F_NEW**: The space under the mapping is newly allocated.
220      If a write fails and the mapping is a space reservation, the
230    * **IOMAP_F_SHARED**: The space under the mapping is shared.
233    * **IOMAP_F_BUFFER_HEAD**: This mapping requires the use of buffer
238      coalesced into this single mapping.
241    * **IOMAP_F_XATTR**: The mapping is for extended attribute data, not
260      based on HW-offload mechanism. They must also ensure that mapping updates
269      using this mapping.
271    * **IOMAP_F_STALE**: The mapping was found to be stale.
272      iomap will call ``->iomap_end`` on this mapping and then
273      ``->iomap_begin`` to obtain a new mapping.
279  * ``bdev`` describes the block device for this mapping.
282  * ``dax_dev`` describes the DAX device for this mapping.
288    This value is ignored for all other mapping types.
307 structure to obtain a mapping and (optionally) to release the mapping:
324 iomap operations call ``->iomap_begin`` to obtain one file mapping for
327 This mapping should be returned through the ``iomap`` pointer.
328 The mapping must cover at least the first byte of the supplied file
354    single iomap mapping.
377 Only pagecache and fsdax operations support reading from one mapping and
384 is called to signal that iomap is finished with a mapping.
400 iomap only handles mapping and I/O.
425      access to the file space mapping information.
432      Filesystems with immutable mapping information may not require
441      For example, pagecache write operations will obtain a file mapping,