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

CONTEXT

67       The process makes block I/O request
68

SEE ALSO

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