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 0/2] docs: ftrace: Clarify the RAM impact of buffer_size_kb
Date: Wed, 13 Nov 2019 11:31:37 -0500 [thread overview]
Message-ID: <cover.1573661658.git.frank@generalsoftwareinc.com> (raw)
Improves the documentation of buffer_size_kb by clarifying how is
calculated the number of allocated pages for the ring buffer.
** Do not apply the second patch **. It's just for illustration
purposes.
Frank A. Cancio Bello (2):
docs: ftrace: Clarify the RAM impact of buffer_size_kb
** do not apply this patch ** Just for illustration purposes
Documentation/trace/ftrace.rst | 13 +++++++++++--
kernel/trace/ring_buffer.c | 2 ++
2 files changed, 13 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-13 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 16:31 Frank A. Cancio Bello [this message]
2019-11-13 16:32 ` [RFC 1/2] docs: ftrace: Clarify the RAM impact of buffer_size_kb Frank A. Cancio Bello
2019-11-13 16:37 ` Steven Rostedt
2019-11-14 20:20 ` Joel Fernandes
2019-11-14 21:36 ` Steven Rostedt
2019-11-15 4:24 ` Frank A. Cancio Bello
2019-11-15 13:30 ` Steven Rostedt
2019-11-15 15:59 ` Frank A. Cancio Bello
2019-11-15 16:03 ` Steven Rostedt
2019-11-13 16:33 ` [RFC 2/2] ** do not apply this patch ** Just for illustration purposes Frank A. Cancio Bello
2019-11-13 21:06 ` kbuild test robot
2019-11-16 10:01 ` kbuild test robot
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.1573661658.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.