The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
	Vincent Donnefort <vdonnefort@google.com>,
	Kent Overstreet <kent.overstreet@gmail.com>
Subject: [for-next][PATCH 13/16] ring-buffer: Add documentation on the buffer_subbuf_order file
Date: Thu, 21 Dec 2023 11:10:37 -0500	[thread overview]
Message-ID: <20231221161105.976193556@goodmis.org> (raw)
In-Reply-To: 20231221161024.478795180@goodmis.org

From: "Steven Rostedt (Google)" <rostedt@goodmis.org>

Add to the documentation how to use the buffer_subbuf_order file to change
the size and how it affects what events can be added to the ring buffer.

Link: https://lore.kernel.org/linux-trace-kernel/20231219185631.230636734@goodmis.org

Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Cc: Vincent Donnefort <vdonnefort@google.com>
Cc: Kent Overstreet <kent.overstreet@gmail.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
 Documentation/trace/ftrace.rst | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
index 23572f6697c0..231d26ceedb0 100644
--- a/Documentation/trace/ftrace.rst
+++ b/Documentation/trace/ftrace.rst
@@ -203,6 +203,33 @@ of ftrace. Here is a list of some of the key files:
 
 	This displays the total combined size of all the trace buffers.
 
+  buffer_subbuf_order:
+
+	This sets or displays the sub buffer page size order. The ring buffer
+	is broken up into several same size "sub buffers". An event can not be
+	bigger than the size of the sub buffer. Normally, the sub buffer is
+	the size of the architecture's page (4K on x86). The sub buffer also
+	contains meta data at the start which also limits the size of an event.
+	That means when the sub buffer is a page size, no event can be larger
+	than the page size minus the sub buffer meta data.
+
+	The buffer_subbuf_order allows the user to change the size of the sub
+	buffer. As the sub buffer is a set of pages by the power of 2, thus
+	the sub buffer total size is defined by the order:
+
+	order		size
+	----		----
+	0		PAGE_SIZE
+	1		PAGE_SIZE * 2
+	2		PAGE_SIZE * 4
+	3		PAGE_SIZE * 8
+
+	Changing the order will change the sub buffer size allowing for events
+	to be larger than the page size.
+
+	Note: When changing the order, tracing is stopped and any data in the
+	ring buffer and the snapshot buffer will be discarded.
+
   free_buffer:
 
 	If a process is performing tracing, and the ring buffer	should be
-- 
2.42.0



  parent reply	other threads:[~2023-12-21 16:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 16:10 [for-next][PATCH 00/16] tracing: Add dynamic sub-buffer size for 6.8 Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 01/16] ring-buffer: Have ring_buffer_print_page_header() be able to access ring_buffer_iter Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 02/16] ring-buffer: Page size per ring buffer Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 03/16] ring-buffer: Add interface for configuring trace sub buffer size Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 04/16] ring-buffer: Set new size of the ring buffer sub page Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 05/16] ring-buffer: Read and write to ring buffers with custom sub buffer size Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 06/16] ring-buffer: Clear pages on error in ring_buffer_subbuf_order_set() failure Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 07/16] ring-buffer: Do no swap cpu buffers if order is different Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 08/16] ring-buffer: Make sure the spare sub buffer used for reads has same size Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 09/16] tracing: Update snapshot order along with main buffer order Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 10/16] tracing: Stop the tracing while changing the ring buffer subbuf size Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 11/16] ring-buffer: Keep the same size when updating the order Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 12/16] ring-buffer: Just update the subbuffers when changing their allocation order Steven Rostedt
2023-12-21 16:10 ` Steven Rostedt [this message]
2023-12-21 16:10 ` [for-next][PATCH 14/16] ringbuffer/selftest: Add basic selftest to test changing subbuf order Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 15/16] tracing: Update subbuffer with kilobytes not page order Steven Rostedt
2023-12-21 16:10 ` [for-next][PATCH 16/16] ring-buffer: Use subbuf_order for buffer page masking Steven Rostedt

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=20231221161105.976193556@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=tz.stoyanov@gmail.com \
    --cc=vdonnefort@google.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