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

CONTEXT

66       The process makes block I/O request
67

SEE ALSO

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