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

CONTEXT

67       The process makes block I/O request
68

SEE ALSO

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