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:31 +0000
committerDarrick J. Wong <[email protected]>2025-05-07 21:25:32 +0000
commitb1e09178b73adf10dc87fba9aee7787a7ad26874 (patch)
tree6fb23e2195b3e0f57892f08984783303cc4937a4 /drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c
parentxfs: add large atomic writes checks in xfs_direct_write_iomap_begin() (diff)
downloadkernel-b1e09178b73adf10dc87fba9aee7787a7ad26874.tar.gz
kernel-b1e09178b73adf10dc87fba9aee7787a7ad26874.zip
xfs: commit CoW-based atomic writes atomically
When completing a CoW-based write, each extent range mapping update is covered by a separate transaction. For a CoW-based atomic write, all mappings must be changed at once, so change to use a single transaction. Note that there is a limit on the amount of log intent items which can be fit into a single transaction, but this is being ignored for now since the count of items for a typical atomic write would be much less than is typically supported. A typical atomic write would be expected to be 64KB or less, which means only 16 possible extents unmaps, which is quite small. Reviewed-by: Darrick J. Wong <[email protected]> [djwong: add tr_atomic_ioend] Reviewed-by: Christoph Hellwig <[email protected]> Signed-off-by: Darrick J. Wong <[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