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

CONTEXT

66       The process signals the transfer is done.
67

SEE ALSO

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