linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v4 0/5] tracing: Introduce configurable ring sub buffer size
Date: Mon, 13 Dec 2021 11:48:20 +0200	[thread overview]
Message-ID: <20211213094825.61876-1-tz.stoyanov@gmail.com> (raw)

From: "Tzvetomir Stoyanov (VMware)" <tstoyanov@vmware.com>

Currently the size of one sub buffer page is global for all buffers and it
is hard coded to one system page. The patch set introduces configurable
ring buffer sub page size, per ring buffer. A new user space interface is
introduced, which allows to change the sub page size of the ftrace buffer, per
ftrace instance.

v4 changes:
 - Do not change the sub buffer size of the temp event buffer per CPU,
   trace_buffered_event. That size if fixed to one system page.
v3 changes:
 - Fixed ring buffer readers and writers to work with custom sub buffer page
   size.
v2 changes:
 - Split code refactoring in a separate patch.
 - Changed the logic to work with order of system pages, instead of page
   size.
 - Fix freeing of the allocated pages, to take into account the actual order.
 - Code clean ups.
 - Bug fixes.

Tzvetomir Stoyanov (VMware) (5):
  [RFC] tracing: Refactor ring buffer implementation
  [RFC] tracing: Page size per ring buffer
  [RFC] tracing: Add interface for configuring trace sub buffer size
  [RFC] tracing: Set new size of the ring buffer sub page
  [RFC] tracing: Read and write to ring buffers with custom sub buffer
    size

 include/linux/ring_buffer.h          |  17 +-
 kernel/trace/ring_buffer.c           | 345 ++++++++++++++++++++-------
 kernel/trace/ring_buffer_benchmark.c |  10 +-
 kernel/trace/trace.c                 |  84 +++++--
 kernel/trace/trace.h                 |   1 +
 kernel/trace/trace_events.c          |  50 +++-
 6 files changed, 392 insertions(+), 115 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-12-13 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  9:48 Tzvetomir Stoyanov (VMware) [this message]
2021-12-13  9:48 ` [PATCH v4 1/5] [RFC] tracing: Refactor ring buffer implementation Tzvetomir Stoyanov (VMware)
2021-12-13  9:48 ` [PATCH v4 2/5] [RFC] tracing: Page size per ring buffer Tzvetomir Stoyanov (VMware)
2021-12-13  9:48 ` [PATCH v4 3/5] [RFC] tracing: Add interface for configuring trace sub buffer size Tzvetomir Stoyanov (VMware)
2021-12-13  9:48 ` [PATCH v4 4/5] [RFC] tracing: Set new size of the ring buffer sub page Tzvetomir Stoyanov (VMware)
2021-12-13  9:48 ` [PATCH v4 5/5] [RFC] tracing: Read and write to ring buffers with custom sub buffer size Tzvetomir Stoyanov (VMware)

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=20211213094825.61876-1-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@vger.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;
as well as URLs for NNTP newsgroup(s).