diff options
author | 2025-05-07 14:18:33 -0700 | |
---|---|---|
committer | 2025-05-07 14:25:32 -0700 | |
commit | 9dffc58f23849783ab2f6c2c9f5af9b94a42666f (patch) | |
tree | 1573a03940d12895cf5fb4c28b073154fc5103cf /tools/perf/scripts/python/export-to-postgresql.py | |
parent | xfs: add xfs_calc_atomic_write_unit_max() (diff) | |
download | linux-rng-9dffc58f23849783ab2f6c2c9f5af9b94a42666f.tar.xz linux-rng-9dffc58f23849783ab2f6c2c9f5af9b94a42666f.zip |
xfs: update atomic write limits
Update the limits returned from xfs_get_atomic_write_{min, max, max_opt)().
No reflink support always means no CoW-based atomic writes.
For updating xfs_get_atomic_write_min(), we support blocksize only and that
depends on HW or reflink support.
For updating xfs_get_atomic_write_max(), for no reflink, we are limited to
blocksize but only if HW support. Otherwise we are limited to combined
limit in mp->m_atomic_write_unit_max.
For updating xfs_get_atomic_write_max_opt(), ultimately we are limited by
the bdev atomic write limit. If xfs_get_atomic_write_max() does not report
> 1x blocksize, then just continue to report 0 as before.
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
[djwong: update comments in the helper functions]
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: John Garry <john.g.garry@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions