Searched refs:blktrace (Results 1 – 12 of 12) sorted by relevance
1 DOCTMP = blktrace.log blktrace.aux blktrace.dvi3 all: blktrace.pdf5 blktrace.tex:6 @touch blktrace.tex8 blktrace.pdf: blktrace.tex9 @latex blktrace.tex10 @latex blktrace.tex11 @dvipdfm -p a4 blktrace15 -rm -f blktrace.pdf $(DOCTMP)
21 \title{blktrace User Guide}22 \author{blktrace: Jens Axboe (jens.axboe@oracle.com)\\31 blktrace is a block layer IO tracing mechanism which provides detailed39 you don't need to patch blktrace support as it is already included.41 \item[blktrace] A utility which transfers event traces from the kernel46 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 provided54 git://git.kernel.org/pub/scm/linux/kernel/git/axboe/blktrace.git bt60 blktrace. Some of the specific instructions below may need to be tailored[all …]
9 LOCAL_C_INCLUDES := external/blktrace/17 LOCAL_SRC_FILES := blktrace.c act_mask.c18 LOCAL_C_INCLUDES := external/blktrace/20 LOCAL_MODULE := blktrace27 LOCAL_C_INCLUDES := external/blktrace/36 LOCAL_C_INCLUDES := external/blktrace/
14 blktrace was integrated into the mainline kernel between 2.6.16 and 2.6.17-rc1.17 git://git.kernel.dk/blktrace.git27 git://git.kernel.dk/blktrace.git38 $ blktrace -d <dev> [ -r debug_path ] [ -o output ] [ -k ] [ -w time ]65 -l Run in network listen mode (blktrace server)140 via blktrace. It will check for valid event formats, forward146 If you want to do live tracing, you can pipe the data between blktrace149 % blktrace -d <device> -o - | blkparse -i -155 % blktrace -l157 to listen to incoming blktrace connections, while the client should use[all …]
4 PROGS = blkparse blktrace verify_blkparse blkrawverify blkiomon28 blktrace: blktrace.o act_mask.o target
38 ${DIRNAME}/blktrace ${TRACEOPTS} -o- $@ | ${DIRNAME}/blkparse ${PARSEOPTS} -i-
49 %doc README doc/blktrace.pdf
21 record and replay IOs captured by the \texttt{blktrace} utility. Attempts26 \item Initiate \texttt{blktrace} to capture traces28 \item Stop \texttt{blktrace}
49 \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 detailed69 \item Run \texttt{blktrace} to collect traces. Here you specify the73 specify the \texttt{-a queue} command line option to \texttt{blktrace}.75 \item While \texttt{blktrace} is running, you run the workload that you78 \item When the work load has completed, you stop the \texttt{blktrace}82 \texttt{blktrace} using the \texttt{btrecord} utility. This will parse83 each trace file created by \texttt{blktrace}, and craft IO descriptions105 \texttt{blktrace} run are used to determine the amount of time between[all …]
11 LOCAL_C_INCLUDES := external/blktrace external/blktrace/btt
1 blktrace Timeline
33 tool called blktrace. As noted in its Users Guide, blktrace40 blktrace is capable of producing tremendous amounts of output in the72 \item Run \texttt{blktrace}, specifying whatever devices and other91 \texttt{blktrace} produces a series of binary files