PROBE::IOBLOCK_TRACE

Section: IO Scheduler and block IO Taps (3stap)
Updated: August 2015
Index Return to Main Contents
 

NAME

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

SYNOPSIS

ioblock_trace.request 
 

VALUES

rw

binary trace for read/write request

sector

beginning sector for the entire bio

devname

block device name

idx

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

p_start_sect

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

bdev

target block device

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

q

request queue on which this bio was queued.

bytes_done

number of bytes transferred

vcnt

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

ino

i-node number of the mapped file

size

total size in bytes

name

name of the probe point

bdev_contains

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

CONTEXT

The process makes block I/O request  

SEE ALSO

tapset::ioblock(3stap)


 

Index

NAME
SYNOPSIS
VALUES
CONTEXT
SEE ALSO

This document was created by man2html, using the manual pages.
Time: 20:06:01 GMT, August 25, 2015