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

CONTEXT

66       The process creating a block IO request.
67

NAME

SYNOPSIS

VALUES

CONTEXT

SEE ALSO