Show Table of Contents
probe::ioblock_trace.request
Name
probe::ioblock_trace.request — Fires just as a generic block I/O request is created for a bio.
Synopsis
ioblock_trace.request
Values
q- request queue on which this bio was queued.
size- total size in bytes
idx- offset into the bio vector array
phys_segments- number of segments in this bio after physical address coalescing is performed. vcnt- bio vector count which represents number of array element (page, offset, length) which make up this I/O request
bdev- target block device
p_start_sect- points to the start sector of the partition structure of the device
ino- i-node number of the mapped file
rw- binary trace for read/write request
name- name of the probe point
sector- beginning sector for the entire bio
bdev_contains- points to the device object which contains the partition (when bio structure represents a partition)
devname- block device name
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
bytes_done- number of bytes transferred
Context
The process makes block I/O request

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.