From: Vincent Donnefort <vdonnefort@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] ring-buffer: Use a macro for static buffer bits
Date: Sat, 5 Sep 2026 14:06:06 +0100 [thread overview]
Message-ID: <apwTvi6sC0xqRvwP@google.com> (raw)
In-Reply-To: <20260904151641.17eae0aa@gandalf.local.home>
On Fri, Sep 04, 2026 at 03:16:41PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> Instead of hard coding 30 for the number of bits used for the static
> buffer ids in two places, create a macro. This way if it changes in the
> future, it will change in all the locations that use it.
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
> kernel/trace/ring_buffer.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 220b8405adfc..b88c75b52e8f 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -335,6 +335,9 @@ static __always_inline unsigned int rb_read_page_capacity(struct buffer_data_rea
> return (PAGE_SIZE << rpage->order) - BUF_PAGE_HDR_SIZE;
> }
>
> +/* The number of bits for static buffer ids */
> +#define RB_STATIC_BITS 30
> +
> /*
> * Note, the buffer_page list must be first. The buffer pages
> * are allocated in cache lines, which means that each buffer
> @@ -350,7 +353,7 @@ struct buffer_page {
> local_t entries; /* entries on this page */
> unsigned long real_end; /* real end of data */
> unsigned order; /* order of the page */
> - u32 id:30; /* ID for external mapping */
> + u32 id:RB_STATIC_BITS; /* ID for external mapping */
> u32 range:1; /* Mapped via a range */
> struct buffer_data_page *page; /* Actual data page */
> };
> @@ -663,7 +666,7 @@ static unsigned long rb_static_max_pages(void)
> * Static ring buffers are using bpage::id and must account for the
> * reader page.
> */
> - return (1UL << 30) - 1;
> + return (1UL << RB_STATIC_BITS) - 1;
> }
>
> struct ring_buffer_iter {
> --
> 2.53.0
>
Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
--
Vincent
prev parent reply other threads:[~2026-09-05 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 19:16 Steven Rostedt
2026-09-05 13:06 ` Vincent Donnefort [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=apwTvi6sC0xqRvwP@google.com \
--to=vdonnefort@google.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
all inboxes | Powered by JetHome®