From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Usama Arif <usamaarif642@gmail.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
kent.overstreet@linux.dev, vbabka@suse.cz, hannes@cmpxchg.org,
rientjes@google.com, roman.gushchin@linux.dev,
harry.yoo@oracle.com, shakeel.butt@linux.dev, 00107082@163.com,
pyyjason@gmail.com, pasha.tatashin@soleen.com,
souravpanda@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] fixup: alloc_tag: mark inaccurate allocation counters in /proc/allocinfo output
Date: Thu, 18 Sep 2025 21:20:58 -0700 [thread overview]
Message-ID: <4e76b94d-9c32-4ec1-b2ec-fc989f1a23ad@infradead.org> (raw)
In-Reply-To: <20250916175639.2368772636d5e543faa5b13b@linux-foundation.org>
Andrew,
On 9/16/25 5:56 PM, Andrew Morton wrote:
> On Tue, 16 Sep 2025 21:50:51 +0100 Usama Arif <usamaarif642@gmail.com> wrote:
>
>>
>>
>> On 16/09/2025 17:01, Suren Baghdasaryan wrote:
>>> Document new "accurate:no" marker.
>>>
>>> Fixes: 39d117e04d15 ("alloc_tag: mark inaccurate allocation counters in /proc/allocinfo output")
>>> Suggested-by: Andrew Morton <akpm@linux-foundation.org>
>>> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
>>> ---
>>> Based on mm-new
>>>
>>> Documentation/filesystems/proc.rst | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>>>
>>> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
>>> index 1776a06571c2..17668f82ff1c 100644
>>> --- a/Documentation/filesystems/proc.rst
>>> +++ b/Documentation/filesystems/proc.rst
>>> @@ -1014,6 +1014,14 @@ If file version is 2.0 or higher then each line may contain additional
>>> For example if the counters are not accurate, the line will be appended with
>>> "accurate:no" pair.
>>>
>>> +Supported markers in v2:
>>> +accurate:no
>>> + Absolute values of the counters in this line are not
>>
>> s/values/value/ maybe? :)
>
> That's OK as-is.
>
>> + accurate because of the failure to allocate storage required
>>
>> s/storage required/memory/
>
> Sure.
>
>
> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: alloc_tag-mark-inaccurate-allocation-counters-in-proc-allocinfo-output-fix-fix
> Date: Tue Sep 16 05:53:33 PM PDT 2025
>
> simplification per Usama, reflow text
>
> Cc: David Rientjes <rientjes@google.com>
> Cc: David Wang <00107082@163.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Kent Overstreet <kent.overstreet@linux.dev>
> Cc: Pasha Tatashin <pasha.tatashin@soleen.com>
> Cc: Roman Gushchin <roman.gushchin@linux.dev>
> Cc: Shakeel Butt <shakeel.butt@linux.dev>
> Cc: Sourav Panda <souravpanda@google.com>
> Cc: Suren Baghdasaryan <surenb@google.com>
> Cc: Usama Arif <usamaarif642@gmail.com>
> Cc: Vlastimil Babka <vbabka@suse.cz>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> Documentation/filesystems/proc.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> --- a/Documentation/filesystems/proc.rst~alloc_tag-mark-inaccurate-allocation-counters-in-proc-allocinfo-output-fix-fix
> +++ a/Documentation/filesystems/proc.rst
> @@ -1016,11 +1016,11 @@ For example if the counters are not accu
>
> Supported markers in v2:
> accurate:no
Please insert a blank line here to prevent a docs warning:
linux-next-20250918/Documentation/filesystems/proc.rst:998: ERROR: Unexpected indentation. [docutils]
Thanks.
> - Absolute values of the counters in this line are not
> - accurate because of the failure to allocate storage required
> - to track some of the allocations made at this location.
> - Deltas in these counters are accurate, therefore counters
> - can be used to track allocation size and count changes.
> + Absolute values of the counters in this line are not accurate
> + because of the failure to allocate memory to track some of the
> + allocations made at this location. Deltas in these counters are
> + accurate, therefore counters can be used to track allocation size
> + and count changes.
>
> Example output.
>
> _
--
~Randy
prev parent reply other threads:[~2025-09-19 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 16:01 Suren Baghdasaryan
2025-09-16 20:50 ` Usama Arif
2025-09-16 22:15 ` Suren Baghdasaryan
2025-09-17 0:56 ` Andrew Morton
2025-09-17 1:23 ` Suren Baghdasaryan
2025-09-19 4:20 ` Randy Dunlap [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=4e76b94d-9c32-4ec1-b2ec-fc989f1a23ad@infradead.org \
--to=rdunlap@infradead.org \
--cc=00107082@163.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pyyjason@gmail.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=usamaarif642@gmail.com \
--cc=vbabka@suse.cz \
/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