Lines Matching refs:be
11 % This program is distributed in the hope that it will be useful,
60 blktrace. Some of the specific instructions below may need to be tailored
65 As noted above, the kernel patch along with the blktrace and blkparse utilities are stored in a git repository. One simple way to get going would be:
78 scope of this document, but the following may be used as a sample template.
187 tracing of devices. The above could also be accomplished by issuing:
216 that the command completed successfully. Tracing SCSI commands can be
218 device. An example of that would be \emph{cdrecord} burning.
223 formatting by blkparse. This would be useful if you want to get
226 To do this, one would specify the device (or devices) to be watched. Then
258 This filesystem will be automatically checked every 27 mounts or
344 to \emph{/sys/kernel/debug} -- this can be overridden with the \emph{-r}
347 \item blktrace defaults to collecting \emph{all} events that can be
356 stored into debugfs files. The size and number of buffers can be
363 be \emph{sda}); and \emph{cpu} identifies a CPU for the event stream.
365 The \emph{device} portion of the event file name can be changed via
368 \item blktrace may also be run concurrently with blkparse to produce
401 The following masks may be passed with the \emph{-a} command line
402 option, multiple filters may be combined via multiple \emph{-a} command
425 originate from a user process, but they may also be initiated by
445 blkparse \emph{may} be run in a \emph{live} manner concurrently with
447 the live option for blktrace. An example would be:
460 \item The format of the output data can be controlled via the \emph{-f}
464 be changed via the \emph{-o} option, or text output can be disabled
465 via the\emph{-O} option. A merged binary stream can be produced using
504 -w \emph{span} & --stopwatch=\emph{span} & Display traces for the \emph{span} specified -- where span can be: \\
535 not reachable by the hardware and must be bounced to a lower memory
537 must be copied to/from kernel buffers. Usually this can be fixed with
552 a \emph{struct request} container must be allocated first.
555 the issuer has to wait for one to be freed.
571 straddle a device or internal zone and needs to be chopped up into
573 to a bad setup of that raid/dm device, but may also just be part of
585 The output from blkparse can be tailored for specific use - in particular,
587 wants to see. The data for fields which can be output include:
628 The following table shows the various actions which may be output.
