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

CONTEXT

63       The process signals the transfer is done.
64

SEE ALSO

66       tapset::ioblock(3stap)
67
68
69
70SystemTap Tapset Reference         June 2018       PROBE::IOBLOCK_TRACE(3stap)
Impressum