]> git.ipfire.org Git - thirdparty/man-pages.git/commit
man/man2/statx.2: Add stx_atomic_write_unit_max_opt
authorJohn Garry <john.g.garry@oracle.com>
Thu, 19 Jun 2025 15:44:55 +0000 (15:44 +0000)
committerAlejandro Colomar <alx@kernel.org>
Sat, 28 Jun 2025 14:51:41 +0000 (16:51 +0200)
commit684b9001d0cd0367daad5d7a7c9e3b7c040e0250
tree128fde87d752ca255d6f8e743a16af97ae0b519b
parent2fc4bf025adba6cb7dbc0beb3ebc2a4df48854ae
man/man2/statx.2: Add stx_atomic_write_unit_max_opt

XFS supports atomic writes - or untorn writes - based on two different
methods:
- HW offload in the disk
- FS method based on out-of-place writes

The value reported in stx_atomic_write_unit_max will be the max size of the
FS-based method.

The max atomic write unit size of the FS-based atomic writes will
typically be much larger than what is capable from the HW offload. However,
FS-based atomic writes will also be typically much slower.

Advertise this HW offload size limit to the user in a new statx member,
stx_atomic_write_unit_max_opt.

We want STATX_WRITE_ATOMIC to get this new member in addition to the
already-existing members, so mention that a value of 0 in
stx_atomic_write_unit_max_opt means that stx_atomic_write_unit_max holds
this optimised limit.

Linux will zero unused statx members, so stx_atomic_write_unit_max_opt
will always hold 0 for older kernel versions which do not support
this FS-based atomic write method (for XFS).

Signed-off-by: John Garry <john.g.garry@oracle.com>
Message-ID: <20250619154455.321848-3-john.g.garry@oracle.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
man/man2/statx.2