1PROBE::IOBLOCK.REQ(3stap)IO Scheduler and block IO TapsPROBE::IOBLOCK.REQ(3stap)
2
3
4

NAME

6       probe::ioblock.request - Fires whenever making a generic block I/O
7       request.
8

SYNOPSIS

10       ioblock.request
11

VALUES

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       hw_segments
24           number of segments after physical and DMA remapping hardware
25           coalescing is performed
26
27       phys_segments
28           number of segments in this bio after physical address coalescing is
29           performed
30
31       idx
32           offset into the bio vector array
33
34       bdev
35           target block device
36
37       bdev_contains
38           points to the device object which contains the partition (when bio
39           structure represents a partition)
40
41       vcnt
42           bio vector count which represents number of array element (page,
43           offset, length) which make up this I/O request
44
45       opf
46           operations and flags
47
48       rw
49           binary trace for read/write request
50
51       ino
52           i-node number of the mapped file
53
54       sector
55           beginning sector for the entire bio
56
57       devname
58           block device name
59
60       p_start_sect
61           points to the start sector of the partition structure of the device
62
63       name
64           name of the probe point
65

CONTEXT

67       The process makes block I/O request
68

SEE ALSO

70       tapset::ioblock(3stap)
71
72
73
74SystemTap Tapset Reference        April 2023         PROBE::IOBLOCK.REQ(3stap)
Impressum