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

CONTEXT

66       The process creating a block IO request.
67

NAME

SYNOPSIS

VALUES

CONTEXT

SEE ALSO