aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c
diff options
context:
space:
mode:
authorJohn Garry <[email protected]>2025-05-07 21:18:33 +0000
committerDarrick J. Wong <[email protected]>2025-05-07 21:25:32 +0000
commit9dffc58f23849783ab2f6c2c9f5af9b94a42666f (patch)
tree1573a03940d12895cf5fb4c28b073154fc5103cf /drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c
parentxfs: add xfs_calc_atomic_write_unit_max() (diff)
downloadkernel-9dffc58f23849783ab2f6c2c9f5af9b94a42666f.tar.gz
kernel-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 <[email protected]> [djwong: update comments in the helper functions] Signed-off-by: Darrick J. Wong <[email protected]> Reviewed-by: Christoph Hellwig <[email protected]> Signed-off-by: John Garry <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c')
0 files changed, 0 insertions, 0 deletions