oracular (3) probe::ioblock_trace.request.3stap.gz

Provided by: systemtap-doc_5.1-4_amd64 bug

NAME

       probe::ioblock_trace.request - Fires just as a generic block I/O request is created for a bio.

SYNOPSIS

       ioblock_trace.request

VALUES

       ino
           i-node number of the mapped file

       p_start_sect
           points to the start sector of the partition structure of the device

       devname
           block device name

       q
           request queue on which this bio was queued.

       bdev
           target block device

       rw
           binary trace for read/write request

       opf
           operations and flags

       bytes_done
           number of bytes transferred

       sector
           beginning sector for the entire bio

       idx
           offset into the bio vector array phys_segments - number of segments in this bio after physical
           address coalescing is performed.

       bdev_contains
           points to the device object which contains the partition (when bio structure represents a partition)

       flags
           see below BIO_UPTODATE 0 ok after I/O completion BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would
           block BIO_EOF 2 out-out-bounds error BIO_SEG_VALID 3 nr_hw_seg valid BIO_CLONED 4 doesn't own data
           BIO_BOUNCED 5 bio is a bounce bio BIO_USER_MAPPED 6 contains user pages BIO_EOPNOTSUPP 7 not
           supported

       vcnt
           bio vector count which represents number of array element (page, offset, length) which make up this
           I/O request

       size
           total size in bytes

       name
           name of the probe point

CONTEXT

       The process makes block I/O request

SEE ALSO

       tapset::ioblock(3stap)