From: Xiang Gao <gxxa03070307@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Vincent Donnefort <vdonnefort@google.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lorenzo Stoakes <ljs@kernel.org>, gao xu <gaoxu2@honor.com>,
yinchuang1@xiaomi.com, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org, Xiang Gao <gaoxiang17@xiaomi.com>
Subject: [PATCH v5 4/4] Documentation: document trace_stats memory_usage_kb
Date: Thu, 5 Nov 2026 22:02:21 +0800 [thread overview]
Message-ID: <20261105140221.44614-5-gaoxiang17@xiaomi.com> (raw)
In-Reply-To: <20261105140221.44614-1-gaoxiang17@xiaomi.com>
Document the trace_stats/memory_usage_kb file, which reports the tracing
ring-buffer memory usage categorized by buffer type and memory source.
Signed-off-by: Xiang Gao <gaoxiang17@xiaomi.com>
---
Documentation/trace/ftrace.rst | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
index 9423722848c6..d7af1e37e6b1 100644
--- a/Documentation/trace/ftrace.rst
+++ b/Documentation/trace/ftrace.rst
@@ -218,6 +218,28 @@ of ftrace. Here is a list of some of the key files:
This displays the total combined size of all the trace buffers.
+ trace_stats/memory_usage_kb:
+
+ This reports the memory consumed by the ring buffers, as opposed to
+ the usable data capacity shown by buffer_size_kb. The value is
+ categorized by buffer type and memory source::
+
+ global:
+ instances:
+ snapshots:
+ persistents:
+ remotes:
+ total_system:
+ total_carveout:
+
+ global, instances, and snapshots come from the page allocator.
+ persistents use reserved memory. remotes are not yet reported and
+ are always zero. total_system is the page-allocator memory, while
+ total_carveout is reserved memory that was never in the free pool.
+
+ The same file is provided under trace_stats/per_cpu/cpuN/, reporting
+ only the buffers belonging to that CPU.
+
buffer_subbuf_size_kb:
This sets or displays the sub buffer size. The ring buffer is broken up
--
2.34.1
prev parent reply other threads:[~2026-11-05 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 14:02 [PATCH v5 0/4] tracing: add ring-buffer memory usage statistics Xiang Gao
2026-11-05 14:02 ` [PATCH v5 1/4] ring-buffer: add ring_buffer_memory_size() Xiang Gao
2026-11-05 14:02 ` [PATCH v5 2/4] tracing: add aggregate buffer memory usage statistics Xiang Gao
2026-11-05 14:02 ` [PATCH v5 3/4] tracing: add per-CPU " Xiang Gao
2026-11-05 14:02 ` Xiang Gao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261105140221.44614-5-gaoxiang17@xiaomi.com \
--to=gxxa03070307@gmail.com \
--cc=donggeunyoo.kernel@gmail.com \
--cc=gaoxiang17@xiaomi.com \
--cc=gaoxu2@honor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=vdonnefort@google.com \
--cc=yinchuang1@xiaomi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®