From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>, Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2] perf doc: Document ring buffer mechanism
Date: Fri, 4 Aug 2023 17:10:27 +0800 [thread overview]
Message-ID: <20230804091027.GC589820@leoy-yangtze.lan> (raw)
In-Reply-To: <ZMwTyVKPn0cRewEc@kernel.org>
On Thu, Aug 03, 2023 at 05:53:29PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Aug 04, 2023 at 12:56:36AM +0800, Leo Yan escreveu:
> > Hi Jon,
> >
> > On Thu, Aug 03, 2023 at 08:34:50AM -0600, Jonathan Corbet wrote:
> > > Leo Yan <leo.yan@linaro.org> writes:
> > >
> > > > In the Linux perf tool, the ring buffer serves not only as a medium for
> > > > transferring PMU event data but also as a vital mechanism for hardware
> > > > tracing using technologies like Intel PT and Arm CoreSight, etc.
> > > >
> > > > Consequently, the ring buffer mechanism plays a crucial role by ensuring
> > > > high throughput for data transfer between the kernel and user space
> > > > while avoiding excessive overhead caused by the ring buffer itself.
> > > >
> > > > This commit documents the ring buffer mechanism in detail. It provides
> > > > an in-depth explanation of the implementation of both the generic ring
> > > > buffer and the AUX ring buffer. Additionally, it covers how these ring
> > > > buffers support various tracing modes and explains the synchronization
> > > > with memory barriers.
> > > >
> > > > Signed-off-by: Leo Yan <leo.yan@linaro.org>
> > > > ---
> > >
> > > So this seems like good material from a very brief scan. I do have to
> > > ask, though: why is it not in RST, and why not put it into the
> > > user-space API book?
> >
> > This documentation is Perf related topic, so my instinct is to place
> > it into the folder tools/perf/Documentation/.
> >
> > Strictly to say, the doc doesn't give formal introduction for the
> > user-space APIs. Given perf ring buffer is a mechanism for exchanging
> > data between the kernel and user space, I am open for placing it in the
> > folder Documentation/userspace-api/.
> >
> > I would like get opinions from the perf maintainers if possible, if we
> > have agreenment I am glad to convert it to RST format.
>
> Yeah, I agree with Jon.
Okay, I will spin a new patch based on this discussion.
Thanks for confirmation.
Leo
prev parent reply other threads:[~2023-08-04 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 3:50 Leo Yan
2023-08-03 10:36 ` Thomas Richter
2023-08-03 11:20 ` Leo Yan
2023-08-03 14:34 ` Jonathan Corbet
2023-08-03 16:56 ` Leo Yan
2023-08-03 20:53 ` Arnaldo Carvalho de Melo
2023-08-04 9:10 ` Leo Yan [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=20230804091027.GC589820@leoy-yangtze.lan \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=corbet@lwn.net \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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®