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

CONTEXT

66       The process creating a block IO request.
67

NAME

SYNOPSIS

VALUES

CONTEXT

SEE ALSO