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

CONTEXT

66       The process signals the transfer is done.
67

SEE ALSO

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