lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 13 Mar 2009 12:05:53 +0900 (JST)
From:	KOSAKI Motohiro <>
To:	Steven Rostedt <>
	Ingo Molnar <>,
	Andrew Morton <>,
	Peter Zijlstra <>,
	Frederic Weisbecker <>,
	Lai Jiangshan <>,
	Steven Rostedt <>
Subject: Re: [PATCH 05/16] tracing: show that buffer size is not expanded

> From: Steven Rostedt <>
> Impact: do not confuse user on small trace buffer sizes
> When the system boots up, the trace buffer is small to conserve memory.
> It is only two pages per online CPU. When the tracer is used, it expands
> to the default value.
> This can confuse the user if they look at the buffer size and see only
> 7, but then later they see 1408.
>  # cat /debug/tracing/buffer_size_kb
> 7
>  # echo sched_switch > /debug/tracing/current_tracer
>  # cat /debug/tracing/buffer_size_kb
> 1408
> This patch tries to help remove this confustion by showing that the
> buffer has not been expanded.
>  # cat /debug/tracing/buffer_size_kb
> 7 (expanded: 1408)


I have one question.
Why souldn't use following output?

sprintf(buf, "%lu\n", trace_buf_size >> 10);

My point is:
  - pure number output can hadle easily.
  - nobody need to know internal memory saving logic.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists