trace-cmd-reset(1) [centos man page]

TRACE-CMD-RESET(1)														TRACE-CMD-RESET(1)

NAME

       trace-cmd-reset - turn off all Ftrace tracing to bring back full performance

SYNOPSIS

       trace-cmd reset [OPTIONS]

DESCRIPTION

       The trace-cmd(1) reset command turns off all tracing of Ftrace. This will bring back the performance of the system before tracing was
       enabled. This is necessary since trace-cmd-record(1), trace-cmd-stop(1) and trace-cmd-extract(1) do not disable the tracer, event after the
       data has been pulled from the buffers. The rational is that the user may want to manually enable the tracer with the Ftrace pseudo file
       system, or examine other parts of Ftrace to see what trace-cmd did. After the reset command happens, the data in the ring buffer, and the
       options that were used are all lost.

OPTIONS

       -b buffer_size
	   When the kernel boots, the Ftrace ring buffer is of a minimal size (3 pages per CPU). The first time the tracer is used, the ring
	   buffer size expands to what it was set for (default 1.4 Megs per CPU).

	       If no more tracing is to be done, this option allows you to shrink the
	       ring buffer down to free up available memory.

	       trace-cmd reset -b 1

SEE ALSO

       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-split(1),
       trace-cmd-list(1), trace-cmd-listen(1)

AUTHOR

       Written by Steven Rostedt, <rostedt@goodmis.org[1]>

RESOURCES

       git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

COPYING

       Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).

NOTES

	1. rostedt@goodmis.org
	   mailto:rostedt@goodmis.org

								    06/11/2014							TRACE-CMD-RESET(1)

TRACE-CMD-EXTRACT(1)													      TRACE-CMD-EXTRACT(1)

NAME

       trace-cmd-extract - extract out the data from the Ftrace Linux tracer.

SYNOPSIS

       trace-cmd extract [OPTIONS]

DESCRIPTION

       The trace-cmd(1) extract is usually used after trace-cmd-start(1) and trace-cmd-stop(1). It can be used after the Ftrace tracer has been
       started manually through the Ftrace pseudo file system.

       The extract command creates a trace.dat file that can be used by trace-cmd-report(1) to read from. It reads the kernel internal ring buffer
       to produce the trace.dat file.

OPTIONS

       -p plugin
	   Although extract does not start any traces, some of the plugins require just reading the output in ASCII format. These are the latency
	   tracers, since the latency tracers have a separate internal buffer. The plugin option is therefore only necessary for the wakeup,
	   wakeup-rt, irqsoff, preemptoff and preemptirqsoff plugins.

	       With out this option, the extract command will extract from the internal
	       Ftrace buffers.

       -O option
	   If a latency tracer is being extracted, and the -p option is used, then there are some Ftrace options that can change the format. This
	   will update those options before extracting. To see the list of options see trace-cmd-list. To enable an option, write its name, to
	   disable the option append the characters no to it. For example: noprint-parent will disable the print-parent option that prints the
	   parent function in printing a function event.

       -o outputfile
	   By default, the extract command will create a trace.dat file. This option will change where the file is written to.

SEE ALSO

       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-reset(1), trace-cmd-split(1),
       trace-cmd-list(1), trace-cmd-listen(1)

AUTHOR

       Written by Steven Rostedt, <rostedt@goodmis.org[1]>

RESOURCES

       git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

COPYING

       Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).

NOTES

	1. rostedt@goodmis.org
	   mailto:rostedt@goodmis.org

								    06/11/2014						      TRACE-CMD-EXTRACT(1)