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 0/6] ring-buffer: Fixes for subbuf resizing and persistent buffers
Date: Mon, 10 Aug 2026 13:56:27 +0100 [thread overview]
Message-ID: <20260810125633.3344684-1-vdonnefort@google.com> (raw)
This series addresses multiple issues discovered with the dynamic ring
buffer resizing.
Changelog:
v3:
- Drop first 3 patches (Rebased on 7.2-rc7)
- Add a patch to align "nr_pages" to unsigned int
- Add a patch to remove useless trace_buffer::cpus
- Add unsigned long cast for rb_subbuf_size()
- subbuf_order fix for rb_free_cpu_buffer() (Sashiko)
- Use __always_inline just like the other accessors for the hot-path.
v2 (https://lore.kernel.org/all/20260806211306.3704194-1-vdonnefort@google.com/):
- Prevent resizing of the persistent ring buffer
- Add missing bpage::order init
- Rework subbuf_size/subbuf_order (Sashiko)
- Remove ring_buffer_per_cpu::mapped
- Dynamically calculate trace_buffer::max_data_size
v1 (https://lore.kernel.org/all/20260805153225.2096152-1-vdonnefort@google.com/
Vincent Donnefort (6):
ring-buffer: Fix subbuf resize concurrency
ring-buffer: Dynamically calculate max_data_size
ring-buffer: Free cpu_buffer->free_page with subbuf_order
ring-buffer: Remove trace_buffer::cpus
ring-buffer: Remove ring_buffer_per_cpu::mapped
ring-buffer: Make nr_pages unsigned int
kernel/trace/ring_buffer.c | 259 +++++++++++++++++++------------------
1 file changed, 136 insertions(+), 123 deletions(-)
base-commit: db2ddb87143519e20a95aa36c60b36107b736a58
--
2.55.0.654.g21b8a5bc05-goog
next reply other threads:[~2026-08-10 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 12:56 Vincent Donnefort [this message]
2026-08-10 12:56 ` [PATCH 1/6] ring-buffer: Fix subbuf resize concurrency Vincent Donnefort
2026-08-10 12:56 ` [PATCH 2/6] ring-buffer: Dynamically calculate max_data_size Vincent Donnefort
2026-08-10 12:56 ` [PATCH 3/6] ring-buffer: Free cpu_buffer->free_page with subbuf_order Vincent Donnefort
2026-08-10 12:56 ` [PATCH 4/6] ring-buffer: Remove trace_buffer::cpus Vincent Donnefort
2026-08-10 12:56 ` [PATCH 5/6] ring-buffer: Remove ring_buffer_per_cpu::mapped Vincent Donnefort
2026-08-10 12:56 ` [PATCH 6/6] ring-buffer: Make nr_pages unsigned int Vincent Donnefort
-- strict thread matches above, loose matches on Subject: below --
2026-08-06 21:13 [PATCH 0/6] ring-buffer: Fixes for subbuf resizing and persistent buffers 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=20260810125633.3344684-1-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