Searched refs:traces (Results 1 – 25 of 51) sorted by relevance
123
| /external/blktrace/btreplay/doc/ |
| D | abstract.tex | 26 \item Initiate \texttt{blktrace} to capture traces
27 \item Generate traces\ldots
29 \item Run \texttt{btrecord} to convert traces into IO records
|
| D | btreplay.tex | 57 traces from the kernel for each IO processed by the block IO layer. The
58 traces provide a complete timeline for each IO processed, including
69 \item Run \texttt{blktrace} to collect traces. Here you specify the
71 the only traces you are interested in are \emph{QUEUE} requests --
72 thus, to save system resources (including storage for traces), one could
79 utility (thus saving all traces over the complete workload).
81 \item You extract the pertinent IO information from the traces saved by
250 [ -F : --find-traces ] Default: Off
277 \subsubsection{\texttt{-F} or \texttt{--find-traces}\\Find Trace Files
364 traces on CPU 0.
[all …]
|
| /external/blktrace/btt/doc/ |
| D | btt.tex | 41 form of multiple individual traces per IO executed during the traced
73 parameters you want. You must save the traces to disk in this step,
94 files into one time-ordered stream of traces for all devices.
141 btt to refer to issue traces. Note that an I is used to refer to
142 \emph{insert} traces.}.
154 \item \emph{Q2Q} which measures the time between queue traces
162 = {Q2C}$ however, typically there are multiple queue traces that
354 \item[Per Process] As traces are emitted, they are tagged with the
358 provided which breaks down the traces according to process ID (name).
364 or kjournald for example). Similarly, completion traces are rarely
[all …]
|
| /external/proguard/examples/ |
| D | library.pro | 17 # traces later on. Keep a fixed source file attribute and all line number
18 # tables to actually get these stack traces.
19 # You can comment this out if you're not interested in stack traces.
|
| D | proguard.pro | 16 # Write out an obfuscation mapping file, for de-obfuscating any stack traces
|
| /external/blktrace/ |
| D | blkrawverify.c | 39 static struct trace_info traces[] = { variable
54 #define N_TRACES (sizeof(traces) / sizeof(struct trace_info))
94 sprintf(buf2, "| %s ", traces[i].string); in act_to_str()
|
| D | README | 151 This has a small risk of displaying some traces a little out of sync, since
152 it will do batch sorts of input events. Similarly, you can do traces over
|
| /external/qemu/docs/ |
| D | ANDROID-ELFF.TXT | 21 * If routine happens to be inlined, library traces inclusion up to the first
|
| /external/blktrace/doc/ |
| D | blktrace.tex | 38 layer to emit event traces. If you run a 2.6.17-rc1 or newer kernel,
41 \item[blktrace] A utility which transfers event traces from the kernel
335 The \emph{blktrace} utility extracts event traces from the kernel (via
412 read & \emph{read} traces \\ \hline
415 write & \emph{write} traces \\ \hline
456 \item If you have saved event traces in blktrace with different output
504 -w \emph{span} & --stopwatch=\emph{span} & Display traces for the \emph{span} specified -- w…
505 …& & \emph{end-time} -- Display traces from time 0 through \emph{end-tim…
507 … & & \emph{start:end-time} -- Display traces from time \emph{start} \\
791 or BIO traces. The \emph{what} parameter describes the action being
|
| /external/bluetooth/glib/docs/ |
| D | debugging.txt | 2 Traps (G_BREAKPOINT) and traces for the debuging
|
| /external/elfutils/libebl/ |
| D | ChangeLog | 41 * libebl.h: Remove last traces of libtool.
|
| /external/bison/tests/ |
| D | calc.at | 366 # We don't count GLR's traces yet, since its traces are somewhat
407 # 1. Remove the traces from observed.
|
| /external/proguard/src/proguard/gui/ |
| D | GUIResources.properties | 61 With the ReTrace part of this GUI you can de-obfuscate your stack traces.\
75 you can de-obfuscate your obfuscated stack traces with ReTrace!\
208 <li>"Sourcefile,LineNumberTable" are necessary for generating stack traces.\
214 It will appear as the file name of the classes in stack traces.</html>
|
| /external/strace/ |
| D | NEWS | 169 classes of system calls, e.g. -efile traces all system calls that
|
| /external/bluetooth/glib/ |
| D | README.in | 181 * Further information such as stack traces may be useful, but
|
| /external/bluetooth/glib/docs/reference/glib/ |
| D | running.sgml | 232 <title>Traps and traces</title>
|
| /external/dnsmasq/po/ |
| D | fr.po | 469 msgstr "Active l'�criture de traces en mode asynchrone. Peut prendre en option la valeur de la long…
914 msgstr "l'�criture de traces en mode asynchrone n'est pas disponible sous Solaris."
1004 msgstr "mode asynchrone d'�criture de traces, la taille maximum de la queue est de %d messages."
1431 msgstr "d�bordement : %d traces perdues"
|
| /external/libxml2/patches/ |
| D | 0001-Add-ICU-support-for-libxml.patch | 54 #define DEBUG_ENCODING /* Define this to get encoding traces */
|
| /external/bison/ |
| D | TODO | 106 used to generate the yydebug traces. Some generic scheme probably
|
| D | NEWS | 547 * Rule line numbers are fixed in traces.
|
| /external/protobuf/ |
| D | aclocal.m4 | 30 # Automake X.Y traces this macro to ensure aclocal.m4 has been
43 # aclocal traces this macro to find the Autoconf version.
|
| /external/libpcap/doc/ |
| D | pcap.txt | 118 The problem of exchanging packet traces becomes more and more
125 This document proposes a new format for dumping packet traces. The
|
| /external/libpcap/ |
| D | INSTALL.txt | 120 tcpdump traces?" item.
|
| /external/v8/ |
| D | ChangeLog | 502 Added stack traces collection to Error objects accessible through
1469 Added support for storing JavaScript stack traces in a stack
|
| /external/bison/data/m4sugar/ |
| D | m4sugar.m4 | 213 # This is for traces only.
1195 # Both used via traces.
|
123