Commit 3e6fb8e9 authored by Joonsoo Kim's avatar Joonsoo Kim Committed by Steven Rostedt

Documentation: describe trace_buf_size parameter more accurately

I'm stuck into panic that too litte free memory is left when I boot with
trace_buf_size parameter. After digging into the problem, I found that
trace_buf_size is the size of trace buffer on each cpu rather than total
size of trace buffer. To prevent victim like me, change description of
trace_buf_size parameter more accurately.

Link: http://lkml.kernel.org/r/1417570760-10620-1-git-send-email-iamjoonsoo.kim@lge.comSigned-off-by: default avatarJoonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
parent eabb8980
...@@ -3477,7 +3477,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted. ...@@ -3477,7 +3477,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
are saved. are saved.
trace_buf_size=nn[KMG] trace_buf_size=nn[KMG]
[FTRACE] will set tracing buffer size. [FTRACE] will set tracing buffer size on each cpu.
trace_event=[event-list] trace_event=[event-list]
[FTRACE] Set and start specified trace events in order [FTRACE] Set and start specified trace events in order
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment