summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/modules.py
diff options
context:
space:
mode:
authorJohn Garry <john.g.garry@oracle.com>2025-05-07 14:18:31 -0700
committerDarrick J. Wong <djwong@kernel.org>2025-05-07 14:25:32 -0700
commitb1e09178b73adf10dc87fba9aee7787a7ad26874 (patch)
tree6fb23e2195b3e0f57892f08984783303cc4937a4 /scripts/gdb/linux/modules.py
parent11ab31909d7cc177fab981cd0d6822a570244599 (diff)
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 <djwong@kernel.org> [djwong: add tr_atomic_ioend] Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: John Garry <john.g.garry@oracle.com>
Diffstat (limited to 'scripts/gdb/linux/modules.py')
0 files changed, 0 insertions, 0 deletions