1TRACE-CMD-RESET(1) [FIXME: manual] TRACE-CMD-RESET(1)
2
3
4
6 trace-cmd-reset - turn off all Ftrace tracing to bring back full
7 performance
8
10 trace-cmd reset [OPTIONS]
11
13 The trace-cmd(1) reset command turns off all tracing of Ftrace. This
14 will bring back the performance of the system before tracing was
15 enabled. This is necessary since trace-cmd-record(1), trace-cmd-stop(1)
16 and trace-cmd-extract(1) do not disable the tracer, event after the
17 data has been pulled from the buffers. The rational is that the user
18 may want to manually enable the tracer with the Ftrace pseudo file
19 system, or examine other parts of Ftrace to see what trace-cmd did.
20 After the reset command happens, the data in the ring buffer, and the
21 options that were used are all lost.
22
24 -b buffer_size
25 When the kernel boots, the Ftrace ring buffer is of a minimal size
26 (3 pages per CPU). The first time the tracer is used, the ring
27 buffer size expands to what it was set for (default 1.4 Megs per
28 CPU).
29
30 If no more tracing is to be done, this option allows you to shrink the
31 ring buffer down to free up available memory.
32
33 trace-cmd reset -b 1
34
36 trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1),
37 trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1),
38 trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1)
39
41 Written by Steven Rostedt, <rostedt@goodmis.org[1]>
42
44 git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
45
47 Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted
48 under the terms of the GNU Public License (GPL).
49
51 1. rostedt@goodmis.org
52 mailto:rostedt@goodmis.org
53
54
55
56[FIXME: source] 03/23/2017 TRACE-CMD-RESET(1)