Home
last modified time | relevance | path

Searched refs:blktrace (Results 1 – 12 of 12) sorted by relevance

/external/blktrace/doc/
DMakefile1 DOCTMP = blktrace.log blktrace.aux blktrace.dvi
3 all: blktrace.pdf
5 blktrace.tex:
6 @touch blktrace.tex
8 blktrace.pdf: blktrace.tex
9 @latex blktrace.tex
10 @latex blktrace.tex
11 @dvipdfm -p a4 blktrace
15 -rm -f blktrace.pdf $(DOCTMP)
Dblktrace.tex21 \title{blktrace User Guide}
22 \author{blktrace: Jens Axboe (jens.axboe@oracle.com)\\
31 blktrace is a block layer IO tracing mechanism which provides detailed
39 you don't need to patch blktrace support as it is already included.
41 \item[blktrace] A utility which transfers event traces from the kernel
46 run in \emph{live} mode directly outputs data collected by blktrace.
49 \subsection{blktrace Download Area}
51 The blktrace and blkparse utilities and associated kernel patch are provided
54 git://git.kernel.org/pub/scm/linux/kernel/git/axboe/blktrace.git bt
60 blktrace. Some of the specific instructions below may need to be tailored
[all …]
/external/blktrace/
DREADME14 blktrace was integrated into the mainline kernel between 2.6.16 and 2.6.17-rc1.
17 git://git.kernel.dk/blktrace.git
27 git://git.kernel.dk/blktrace.git
34 A blktrace visualization tool, iowatcher, was added to blktrace in version
40 $ blktrace -d <dev> [ -r debug_path ] [ -o output ] [ -k ] [ -w time ]
67 -l Run in network listen mode (blktrace server)
142 via blktrace. It will check for valid event formats, forward
148 If you want to do live tracing, you can pipe the data between blktrace
151 % blktrace -d <device> -o - | blkparse -i -
157 % blktrace -l
[all …]
DMETADATA1 name: "blktrace"
3 "blktrace is a block layer IO tracing mechanism which provides detailed "
9 value: "http://git.kernel.dk/?p=blktrace.git;a=summary"
DAndroid.bp57 "external/blktrace",
58 "external/blktrace/btt",
88 name: "blktrace",
91 "blktrace.c",
100 include_dirs: ["external/blktrace/"],
DMakefile4 PROGS = blkparse blktrace verify_blkparse blkrawverify blkiomon
31 blktrace: blktrace.o act_mask.o target
Dbtrace38 ${DIRNAME}/blktrace ${TRACEOPTS} -o- $@ | ${DIRNAME}/blkparse ${PARSEOPTS} -i-
Dbtrace.spec49 %doc README doc/blktrace.pdf
/external/blktrace/btreplay/doc/
Dabstract.tex21 record and replay IOs captured by the \texttt{blktrace} utility. Attempts
26 \item Initiate \texttt{blktrace} to capture traces
28 \item Stop \texttt{blktrace}
Dbtreplay.tex49 \texttt{blktrace}\footnote{\texttt{git://git.kernel.dk/blktrace.git}}
50 directory, as it includes \texttt{../blktrace} in the \texttt{Makefile}.
56 The \texttt{blktrace} utility provides the ability to collect detailed
69 \item Run \texttt{blktrace} to collect traces. Here you specify the
73 specify the \texttt{-a queue} command line option to \texttt{blktrace}.
75 \item While \texttt{blktrace} is running, you run the workload that you
78 \item When the work load has completed, you stop the \texttt{blktrace}
82 \texttt{blktrace} using the \texttt{btrecord} utility. This will parse
83 each trace file created by \texttt{blktrace}, and craft IO descriptions
105 \texttt{blktrace} run are used to determine the amount of time between
[all …]
/external/blktrace/btt/
DREADME1 blktrace Timeline
/external/blktrace/btt/doc/
Dbtt.tex33 tool called blktrace. As noted in its Users Guide, blktrace
40 blktrace is capable of producing tremendous amounts of output in the
72 \item Run \texttt{blktrace}, specifying whatever devices and other
91 \texttt{blktrace} produces a series of binary files