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

CONTEXT

66       The process signals the transfer is done.
67

SEE ALSO

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