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       bytes_done
14           number of bytes transferred
15
16       bdev_contains
17           points to the device object which contains the partition (when bio
18           structure represents a partition)
19
20       devname
21           block device name
22
23       bdev
24           target block device
25
26       idx
27           offset into the bio vector array phys_segments - number of segments
28           in this bio after physical address coalescing is performed.
29
30       opf
31           operations and flags
32
33       size
34           total size in bytes
35
36       p_start_sect
37           points to the start sector of the partition structure of the device
38
39       vcnt
40           bio vector count which represents number of array element (page,
41           offset, length) which make up this I/O request
42
43       ino
44           i-node number of the mapped file
45
46       rw
47           binary trace for read/write request
48
49       name
50           name of the probe point
51
52       sector
53           beginning sector for the entire bio
54
55       q
56           request queue on which this bio was queued.
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         May 2019        PROBE::IOBLOCK_TRACE(3stap)
Impressum