Linux Trace Kernel
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
	 linux-trace-kernel@vger.kernel.org
Cc: mathieu.desnoyers@efficios.com, kernel-team@android.com,
	 linux-kernel@vger.kernel.org,
	Vincent Donnefort <vdonnefort@google.com>
Subject: [PATCH v3 05/18] tracing/simple_ring_buffer: Add support for compressed length
Date: Tue, 21 Jul 2026 11:35:50 +0100	[thread overview]
Message-ID: <20260721103603.342266-6-vdonnefort@google.com> (raw)
In-Reply-To: <20260721103603.342266-1-vdonnefort@google.com>

The array length is the total size in bytes of the data for the current
event. It is possible to compress this value into the event header type,
which has 28 unused types, saving 32 bits for sufficiently small events.

The compressed length is expressed as a multiple of the ring-buffer
alignment, 4-bytes by default. Enforces this alignment.

Signed-off-by: Vincent Donnefort <vdonnefort@google.com>

diff --git a/kernel/trace/simple_ring_buffer.c b/kernel/trace/simple_ring_buffer.c
index f4642f5adda3..1a97d17cca24 100644
--- a/kernel/trace/simple_ring_buffer.c
+++ b/kernel/trace/simple_ring_buffer.c
@@ -207,7 +207,15 @@ static unsigned long rb_event_size(unsigned long length)
 {
 	struct ring_buffer_event *event;
 
-	return length + RB_EVNT_HDR_SIZE + sizeof(event->array[0]);
+	if (!length)
+		length++;
+
+	length = ALIGN(length, RB_ALIGNMENT);
+
+	if (length > RB_MAX_SMALL_DATA)
+		length += sizeof(event->array[0]);
+
+	return length + RB_EVNT_HDR_SIZE;
 }
 
 static struct ring_buffer_event *
@@ -223,12 +231,15 @@ rb_event_add_ts_extend(struct ring_buffer_event *event, u64 delta)
 static struct ring_buffer_event *
 simple_rb_reserve_next(struct simple_rb_per_cpu *cpu_buffer, unsigned long length, u64 timestamp)
 {
-	unsigned long ts_ext_size = 0, event_size = rb_event_size(length);
 	struct simple_buffer_page *tail = cpu_buffer->tail_page;
+	unsigned long event_size, array_size, ts_ext_size = 0;
 	struct ring_buffer_event *event;
 	u32 write, prev_write;
 	u64 time_delta;
 
+	event_size = rb_event_size(length);
+	array_size = event_size - RB_EVNT_HDR_SIZE;
+
 	time_delta = timestamp - cpu_buffer->write_stamp;
 
 	if (test_time_stamp(time_delta))
@@ -259,9 +270,13 @@ simple_rb_reserve_next(struct simple_rb_per_cpu *cpu_buffer, unsigned long lengt
 		time_delta = 0;
 	}
 
-	event->type_len = 0;
+	if (length > RB_MAX_SMALL_DATA) {
+		event->type_len = 0;
+		event->array[0] = array_size;
+	} else {
+		event->type_len = DIV_ROUND_UP(array_size, RB_ALIGNMENT);
+	}
 	event->time_delta = time_delta;
-	event->array[0] = event_size - RB_EVNT_HDR_SIZE;
 
 	return event;
 }
@@ -284,7 +299,7 @@ void *simple_ring_buffer_reserve(struct simple_rb_per_cpu *cpu_buffer, unsigned
 
 	rb_event = simple_rb_reserve_next(cpu_buffer, length, timestamp);
 
-	return &rb_event->array[1];
+	return rb_event->type_len ? &rb_event->array[0] : &rb_event->array[1];
 }
 EXPORT_SYMBOL_GPL(simple_ring_buffer_reserve);
 
-- 
2.55.0.229.g6434b31f56-goog


  parent reply	other threads:[~2026-07-21 10:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 10:35 [PATCH v3 00/18] tracing/remotes: Add printk, dump_on_panic and boot parameters Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 01/18] tracing/remotes: Gate tracefs files opening on trace remote registration Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 02/18] tracing/remotes: Release tracefs,eventfs on registration failure Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 03/18] tracing/remotes: Use kstrtobool for boolean tracefs files Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 04/18] tracing/remotes: Use a single per-remote polling work Vincent Donnefort
2026-07-21 10:35 ` Vincent Donnefort [this message]
2026-07-21 10:35 ` [PATCH v3 06/18] tracing/remotes: Add dmesg tracefs file Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 07/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 08/18] tracing/remotes: selftests: Prefix hypervisor folder Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 09/18] ring-buffer: Use irqsave for the reader lock in ring_buffer_poll_remote Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 10/18] ring-buffer: Use panic-friendly locking in ring_buffer_iter interface Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 11/18] ring-buffer: Add ring_buffer_read_remote_meta_page() Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 12/18] ring-buffer: Add kerneldoc for ring_buffer_poll_remote Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 13/18] tracing/remotes: Add dump_on_panic tracefs file Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 14/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 15/18] tracing/remotes: Add poll_ms " Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 16/18] tracing/remotes: Add trace_remote cmdline options Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 17/18] Documentation: tracing/remotes: Add detailed tracefs layout Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 18/18] Documentation/kernel-parameters: Add trace_remote Vincent Donnefort

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=20260721103603.342266-6-vdonnefort@google.com \
    --to=vdonnefort@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    /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