1PROBE::IOBLOCK_TRACE(3staIpO)Scheduler and block IO TaPpRsOBE::IOBLOCK_TRACE(3stap)
2
3
4
6 probe::ioblock_trace.request - Fires just as a generic block I/O
7 request is created for a bio.
8
10 ioblock_trace.request
11
13 flags
14 see below BIO_UPTODATE 0 ok after I/O completion BIO_RW_BLOCK 1
15 RW_AHEAD set, and read/write would block BIO_EOF 2 out-out-bounds
16 error BIO_SEG_VALID 3 nr_hw_seg valid BIO_CLONED 4 doesn't own data
17 BIO_BOUNCED 5 bio is a bounce bio BIO_USER_MAPPED 6 contains user
18 pages BIO_EOPNOTSUPP 7 not supported
19
20 size
21 total size in bytes
22
23 p_start_sect
24 points to the start sector of the partition structure of the device
25
26 rw
27 binary trace for read/write request
28
29 sector
30 beginning sector for the entire bio
31
32 idx
33 offset into the bio vector array phys_segments - number of segments
34 in this bio after physical address coalescing is performed.
35
36 devname
37 block device name
38
39 name
40 name of the probe point
41
42 bdev
43 target block device
44
45 bytes_done
46 number of bytes transferred
47
48 ino
49 i-node number of the mapped file
50
51 opf
52 operations and flags
53
54 vcnt
55 bio vector count which represents number of array element (page,
56 offset, length) which make up this I/O request
57
58 q
59 request queue on which this bio was queued.
60
61 bdev_contains
62 points to the device object which contains the partition (when bio
63 structure represents a partition)
64
66 The process makes block I/O request
67
69 tapset::ioblock(3stap)
70
71
72
73SystemTap Tapset Reference May 2021 PROBE::IOBLOCK_TRACE(3stap)