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

CONTEXT

66       The process signals the transfer is done.
67

SEE ALSO

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