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