'\" t
.\"     Title: trace-cmd-reset
.\"    Author: [see the "AUTHOR" section]
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\"      Date: 06/20/2014
.\"    Manual: \ \&
.\"    Source: \ \&
.\"  Language: English
.\"
.TH "TRACE\-CMD\-RESET" "1" "06/20/2014" "\ \&" "\ \&"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
trace-cmd-reset \- turn off all Ftrace tracing to bring back full performance
.SH "SYNOPSIS"
.sp
\fBtrace\-cmd reset\fR [\fIOPTIONS\fR]
.SH "DESCRIPTION"
.sp
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 \fItrace\-cmd\-record(1)\fR, \fItrace\-cmd\-stop(1)\fR and \fItrace\-cmd\-extract(1)\fR 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\&.
.SH "OPTIONS"
.PP
\fB\-b\fR \fIbuffer_size\fR
.RS 4
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)\&.
.sp
.if n \{\
.RS 4
.\}
.nf
If no more tracing is to be done, this option allows you to shrink the
ring buffer down to free up available memory\&.
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
trace\-cmd reset \-b 1
.fi
.if n \{\
.RE
.\}
.RE
.PP
\fB\-B\fR \fIbuffer\-name\fR
.RS 4
If the kernel supports multiple buffers, this will reset the trace for only the given buffer\&. It does not affect any other buffer\&. This may be used multiple times to specify different buffers\&. The top level buffer will not be reset if this option is given (unless the
\fB\-t\fR
option is also supplied)\&.
.RE
.PP
\fB\-d\fR
.RS 4
Delete the previously specified buffer instance that was specified by the
\fB\-B\fR
option\&. It is invalid to use with
\fB\-t\fR
as the top level instance can not be deleted\&.
.RE
.PP
\fB\-t\fR
.RS 4
Resets the top level instance buffer\&. Without the
\fB\-B\fR
option this is the same as the default\&. But if
\fB\-B\fR
is used, this is required if the top level instance buffer should also be reset\&.
.RE
.SH "SEE ALSO"
.sp
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)
.SH "AUTHOR"
.sp
Written by Steven Rostedt, <\m[blue]\fBrostedt@goodmis\&.org\fR\m[]\&\s-2\u[1]\d\s+2>
.SH "RESOURCES"
.sp
git://git\&.kernel\&.org/pub/scm/linux/kernel/git/rostedt/trace\-cmd\&.git
.SH "COPYING"
.sp
Copyright (C) 2010 Red Hat, Inc\&. Free use of this software is granted under the terms of the GNU Public License (GPL)\&.
.SH "NOTES"
.IP " 1." 4
rostedt@goodmis.org
.RS 4
\%mailto:rostedt@goodmis.org
.RE