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

CONTEXT

66       The process creating a block IO request.
67

NAME

SYNOPSIS

VALUES

CONTEXT

SEE ALSO