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

NAME

6       probe::ioblock_trace.end - Fires whenever a block I/O transfer is
7       complete.
8

SYNOPSIS

10       ioblock_trace.end
11

VALUES

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

CONTEXT

66       The process signals the transfer is done.
67

SEE ALSO

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