From: Christian Loehle <christian.loehle@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Zheng Yejian <zhengyejian1@huawei.com>,
mhiramat@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] tracing: document buffer_size_kb more precisely
Date: Tue, 3 Oct 2023 16:01:30 +0100 [thread overview]
Message-ID: <e89de62e-e19a-1eeb-d180-a308cbf97c03@arm.com> (raw)
In-Reply-To: <20231002110935.2fde6637@gandalf.local.home>
On 02/10/2023 16:09, Steven Rostedt wrote:
> On Tue, 26 Sep 2023 11:38:14 +0100
> Christian Loehle <christian.loehle@arm.com> wrote:
>
>>>> @@ -191,7 +191,7 @@ of ftrace. Here is a list of some of the key files:
>>>> A few extra pages may be allocated to accommodate buffer management
>>>> meta-data. If the last page allocated has room for more bytes
>>>> than requested, the rest of the page will be used,
>>>> - making the actual allocation bigger than requested or shown.
>>>> + making the actual allocation bigger than requested.
>>>
>>> Hi, the actual allocation should still be bigger than shown due to the
>>> loss of accuracy when doing unit conversion from bytes to kilobytes (see
>>> tracing_entries_read()).
>>>
>> Right, the sysfs obviously only allows for KB aligned setting, but you're right.
>> If set on the cmdline non-KB multiples are possible and accuracy is lost.
>> Nevermind then.
>
> I'm assuming this patch can be dropped?
>
> -- Steve
Yes please drop it, there's probably still some room for improvement for clarity,
but this patch is not correct.
prev parent reply other threads:[~2023-10-03 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 10:02 [PATCH] tracing: document buffer_size_kb more precisely Christian Loehle
2023-09-25 11:44 ` Zheng Yejian
2023-09-26 10:38 ` Christian Loehle
2023-10-02 15:09 ` Steven Rostedt
2023-10-03 15:01 ` Christian Loehle [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=e89de62e-e19a-1eeb-d180-a308cbf97c03@arm.com \
--to=christian.loehle@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=zhengyejian1@huawei.com \
/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).