1PROBE::IOBLOCK.REQ(3stap)IO Scheduler and block IO TapsPROBE::IOBLOCK.REQ(3stap)
2
3
4

NAME

6       probe::ioblock.request - Fires whenever making a generic block I/O
7       request.
8

SYNOPSIS

10       ioblock.request
11

VALUES

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

CONTEXT

67       The process makes block I/O request
68

SEE ALSO

70       tapset::ioblock(3stap)
71
72
73
74SystemTap Tapset Reference       November 2020       PROBE::IOBLOCK.REQ(3stap)
Impressum