1PROBE::IOBLOCK_TRACE(3staIpO)Scheduler and block IO TaPpRsOBE::IOBLOCK_TRACE(3stap)
2
3
4

NAME

6       probe::ioblock_trace.request - Fires just as a generic block I/O
7       request is created for a bio.
8

SYNOPSIS

10       ioblock_trace.request
11

VALUES

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

CONTEXT

66       The process makes block I/O request
67

SEE ALSO

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