1PROBE::IOBLOCK_TRACE(3staIpO)Scheduler and block IO TaPpRsOBE::IOBLOCK_TRACE(3stap)
2
3
4

NAME

6       probe::ioblock_trace.request - Fires just as a generic block I/O
7       request is created for a bio.
8

SYNOPSIS

10       ioblock_trace.request
11

VALUES

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

CONTEXT

66       The process makes block I/O request
67

SEE ALSO

69       tapset::ioblock(3stap)
70
71
72
73SystemTap Tapset Reference        April 2023       PROBE::IOBLOCK_TRACE(3stap)
Impressum