Lines Matching +full:buffered +full:- +full:negative
1 .. SPDX-License-Identifier: GPL-2.0
78 1. Obtain a space mapping via ``->iomap_begin``
80 2. For each sub-unit of work...
89 4. Release the mapping via ``->iomap_end``, if necessary
105 -----------
127 device pre-shutdown hook from returning before other threads have
152 ----------------
158 .. code-block:: c
192 ``->iomap_end`` function must delete the reservation.
211 For write operation, the ``->iomap_end`` function presumably
216 These flags should be set by the filesystem in ``->iomap_begin``:
248 (e.g. ZNS devices). This flag applies only to buffered I/O writeback; all
259 inform iomap that the write I/O operation requires torn-write protection
260 based on HW-offload mechanism. They must also ensure that mapping updates
265 The filesystem should supply an ``->iomap_end`` function if it needs
272 iomap will call ``->iomap_end`` on this mapping and then
273 ``->iomap_begin`` to obtain a new mapping.
290 * ``private`` is a pointer to `filesystem-private information
291 <https://lore.kernel.org/all/20180619164137.13720-7-hch@lst.de/>`_.
292 This value will be passed unchanged to ``->iomap_end``.
298 should not be held between ``->iomap_begin`` and ``->iomap_end``.
304 --------------------
309 .. code-block:: c
321 ``->iomap_begin``
324 iomap operations call ``->iomap_begin`` to obtain one file mapping for
334 operation-specific sections below.
342 memory-like storage.
347 This is similar in intent to ``O_NONBLOCK`` for network APIs - it is
363 then they should return ``-EAGAIN`` as early as possible rather than
369 buffered file I/O and would like the kernel to drop the pagecache
374 <https://lore.kernel.org/all/20191008071527.29304-9-hch@lst.de/>`_
380 ``->iomap_end``
383 After the operation completes, the ``->iomap_end`` function, if present,
386 context that were set up in ``->iomap_begin``.
391 ``flags`` will contain the same value passed to ``->iomap_begin``.
394 Both functions should return a negative errno code on error, or zero on
424 ``->iomap_begin`` and ``->iomap_end`` functions to coordinate
457 * Does iomap *actually* work for non-regular file data?