probe::ioblock.request(3stap)

probe::ioblock.request3stap

Fires whenever making a generic block i/o request.

Usage

ioblock.request 

Values

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

name

name of the probe point

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

sector

beginning sector for the entire bio

bdev_contains

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

idx

offset into the bio vector array

phys_segments

number of segments in this bio after physical address coalescing is performed

opf

operations and flags

hw_segments

number of segments after physical and DMA remapping hardware coalescing is performed

rw

binary trace for read/write request

ino

i-node number of the mapped file

p_start_sect

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

bdev

target block device

devname

block device name

Context

The process makes block I/O request

See ALSO0

tapset::ioblock(3stap)

Releases

8 releases since Debian 6.0 (Squeeze); the text changed 7 times.

  1. 6.0
  2. 7
  3. 8
  4. 9
  5. 10
  6. 11
  7. 12
  8. 13

From systemtap-doc 5.1-5 in Debian 13 (Trixie). Parsed by carta from the page's man source.