From: "Frank A. Cancio Bello" <frank@generalsoftwareinc.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: joel@joelfernandes.org, saiprakash.ranjan@codeaurora.org
Subject: [RFC v2 0/2] docs: ftrace: Clarify the RAM impact of buffer_size_kb
Date: Sun, 24 Nov 2019 23:37:37 -0500 [thread overview]
Message-ID: <cover.1574655670.git.frank@generalsoftwareinc.com> (raw)
Clarifies the RAM footprint of buffer_size_kb without getting into
implementation details.
Changes in v2:
- Removes implementation description of the RAM footprint of
buffer_size_kb, but still make the corresponded clarification.
- Removes a patch that was just for illustration purposes because
Steven already got the issue that I was referring to.
- Adds a patch to fix other typos in the doc.
Frank A. Cancio Bello (2):
docs: ftrace: Clarify the RAM impact of buffer_size_kb
docs: ftrace: Fix typos
Documentation/trace/ftrace.rst | 9 +++++----
Documentation/trace/ring-buffer-design.txt | 2 +-
2 files changed, 6 insertions(+), 5 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-25 4:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 4:37 Frank A. Cancio Bello [this message]
2019-11-25 4:38 ` [RFC v2 1/2] docs: ftrace: Clarify the RAM impact of buffer_size_kb Frank A. Cancio Bello
2019-11-25 4:38 ` [RFC v2 2/2] docs: ftrace: Fix typos Frank A. Cancio Bello
2019-11-25 17:37 ` Steven Rostedt
2019-11-25 21:46 ` Steven Rostedt
2019-11-25 23:49 ` Frank A. Cancio Bello
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=cover.1574655670.git.frank@generalsoftwareinc.com \
--to=frank@generalsoftwareinc.com \
--cc=corbet@lwn.net \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=saiprakash.ranjan@codeaurora.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).