probe::ioblock_trace.bounce(3stap)

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

NAME

6       probe::ioblock_trace.bounce - Fires whenever a buffer bounce is needed
7       for at least one page of a block IO request.
8

SYNOPSIS

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

CONTEXT

66       The process creating a block IO request.
67

NAME

SYNOPSIS

VALUES

CONTEXT

SEE ALSO