Lines Matching refs:iomap
20 iomap is a filesystem library for handling common file operations.
63 the basis of that unit, the iomap model asks the filesystem for the
73 At a high level, an iomap operation `looks like this
91 Each iomap operation will be covered in more detail below.
94 <https://kernelnewbies.org/KernelProjects/iomap>`_.
97 design and capabilities of iomap, followed by a more detailed catalog
98 of the interfaces presented by iomap.
99 If you change iomap, please update this design document.
136 * **iomap internal operation lock**: This is a general term for
137 synchronization primitives that iomap functions take while holding a
151 ``struct iomap``
154 The filesystem communicates to the iomap iterator the mapping of
160 struct iomap {
186 iomap does not support writing (whether via pagecache or direct
259 inform iomap that the write I/O operation requires torn-write protection
264 These flags can be set by iomap itself during file operations.
272 iomap will call ``->iomap_end`` on this mapping and then
306 Every iomap function requires the filesystem to pass an operations
313 unsigned flags, struct iomap *iomap,
314 struct iomap *srcmap);
318 struct iomap *iomap);
324 iomap operations call ``->iomap_begin`` to obtain one file mapping for
327 This mapping should be returned through the ``iomap`` pointer.
331 Each iomap operation describes the requested operation through the
335 These flags can, at least in principle, apply generally to iomap
354 single iomap mapping.
384 is called to signal that iomap is finished with a mapping.
392 iomap ops for reads are not likely to need to supply this function.
400 iomap only handles mapping and I/O.
409 iomap requires that filesystems supply their own locking model.
411 iomap is concerned:
414 coordinate access to different iomap operations.
426 The fields of the iomap object should be filled out while holding
435 * The **operation** primitive is taken by an iomap operation to
457 * Does iomap *actually* work for non-regular file data?