From: Suren Baghdasaryan <surenb@google.com>
To: Usama Arif <usamaarif642@gmail.com>
Cc: akpm@linux-foundation.org, 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: Tue, 16 Sep 2025 22:15:49 +0000 [thread overview]
Message-ID: <CAJuCfpFc=qUAnS=-YuW_CRgF6GUz-7_ZEMFEL-n+XY6MAr7ytg@mail.gmail.com> (raw)
In-Reply-To: <4c4e97c1-7f93-4c09-a235-ab169a998ef0@gmail.com>
On Tue, Sep 16, 2025 at 8:50 PM 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? :)> + accurate because of the failure to allocate storage required
Maybe... English is not my first or second language, so I'm not really sure...
>
> s/storage required/memory/
I'm fine with the proposed changes. Andrew, if you agree with them,
could you please fold them in when you pick up this patch?
>
> > + 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.
> >
> > ::
> >
> > base-commit: 199236646ffd82b5a5bcf2bca1579ea06cb0ae74
>
next prev parent reply other threads:[~2025-09-16 22:16 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 [this message]
2025-09-17 0:56 ` Andrew Morton
2025-09-17 1:23 ` Suren Baghdasaryan
2025-09-19 4:20 ` Randy Dunlap
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='CAJuCfpFc=qUAnS=-YuW_CRgF6GUz-7_ZEMFEL-n+XY6MAr7ytg@mail.gmail.com' \
--to=surenb@google.com \
--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=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