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

CONTEXT

66       The process signals the transfer is done.
67

SEE ALSO

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