Re: [PATCH v2] traceevent/block: Add REQ_ATOMIC flag to block trace events

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 22 May 2025 19:21:10 +0530, Ritesh Harjani (IBM) wrote:
> Filesystems like XFS can implement atomic write I/O using either
> REQ_ATOMIC flag set in the bio or via CoW operation. It will be useful
> if we have a flag in trace events to distinguish between the two. This
> patch adds char 'U' (Untorn writes) to rwbs field of the trace events
> if REQ_ATOMIC flag is set in the bio.
> 
> <W/ REQ_ATOMIC>
> =================
> xfs_io-4238    [009] .....  4148.126843: block_rq_issue: 259,0 WFSU 16384 () 768 + 32 none,0,0 [xfs_io]
> <idle>-0       [009] d.h1.  4148.129864: block_rq_complete: 259,0 WFSU () 768 + 32 none,0,0 [0]
> 
> [...]

Applied, thanks!

[1/1] traceevent/block: Add REQ_ATOMIC flag to block trace events
      commit: 927244f6efff6df5f8f2ab58c7d1eec9f90cc3f2

Best regards,
-- 
Jens Axboe







[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux