Lines Matching refs:iomap

17 Below are a discussion of the high level file operations that iomap
29 iomap implements nearly all the folio and pagecache management that
35 linked lists of buffer heads instead of the per-folio bitmaps that iomap
44 The following iomap functions can be referenced directly from the
70      bool (*iomap_valid)(struct inode *inode, const struct iomap *iomap);
75 iomap calls these functions:
79     If this function is not provided, iomap will call
87     If this function is not provided, iomap will ``folio_unlock`` and
107     lock has been taken so that iomap can manage the folio correctly.
117     ``->iomap_begin`` function may set ``struct iomap::validity_cookie``
118     at the same time that it populates the other iomap fields.
122     iomap::validity_cookie`` during ``->iomap_begin``.
125     ``->iomap_valid``, then the iomap should considered stale and the
129     be written to. If this function is not provided, iomap will default to
132 These ``struct kiocb`` flags are significant for buffered I/O with iomap:
147 If the fsblock size is less than the size of a pagecache folio, iomap
149 This enables iomap to handle both "bs < ps" `filesystems
153 iomap internally tracks two state bits per fsblock:
155  * ``uptodate``: iomap will try to keep folios fully up to date.
161  * ``dirty``: iomap will set the per-block dirty state when programs
166 iomap also tracks the amount of read and write disk IOs that are in
295   - ``writeback_range``: Sets ``wpc->iomap`` to the space mapping of the file
297     iomap calls this function for each dirty fs block in each dirty folio,
303     Do not return ``IOMAP_DELALLOC`` mappings here; iomap currently
308     unclear if ``iomap::validity_cookie`` can be reused for this
335 completes, iomap creates chains of ``struct iomap_ioend`` objects that
337 By default, iomap finishes writeback ioends by clearing the writeback
355 iomap ioends contain a ``list_head`` to enable batching.
357 Given a batch of ioends, iomap has a few helpers to assist with
433 These ``struct kiocb`` flags are significant for direct I/O with iomap:
470    iomap itself will return this value if it cannot invalidate the page
533    The filesystems must set IOMAP_F_ATOMIC_BIO to inform iomap core of an
563   - ``submit_io``: iomap calls this function when it has constructed a
629    iomap infrastructure to perform a pure overwrite, it must fail the
645 Callers commonly hold the same locks as they do to call their iomap
652 iomap pagecache I/O counterparts.
660 Callers commonly hold the same locks as they do to call their iomap
667 ``dax_remap_file_range_prep`` function with their own iomap read ops.
672 iomap implements the two iterating whence modes of the ``llseek`` system
721 iomap implements two of the file space mapping system calls.