[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJuCfpHQMcGJBu=qjN6Qy0XqmLikqeWfm6SW+S9orOPk=m21Lw@mail.gmail.com>
Date: Tue, 16 Sep 2025 18:23:41 -0700
From: Suren Baghdasaryan <surenb@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Usama Arif <usamaarif642@...il.com>, kent.overstreet@...ux.dev, vbabka@...e.cz,
hannes@...xchg.org, rientjes@...gle.com, roman.gushchin@...ux.dev,
harry.yoo@...cle.com, shakeel.butt@...ux.dev, 00107082@....com,
pyyjason@...il.com, pasha.tatashin@...een.com, souravpanda@...gle.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] fixup: alloc_tag: mark inaccurate allocation counters
in /proc/allocinfo output
On Tue, Sep 16, 2025 at 5:56 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Tue, 16 Sep 2025 21:50:51 +0100 Usama Arif <usamaarif642@...il.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@...ux-foundation.org>
> > > Signed-off-by: Suren Baghdasaryan <surenb@...gle.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@...ux-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@...gle.com>
> Cc: David Wang <00107082@....com>
> Cc: Johannes Weiner <hannes@...xchg.org>
> Cc: Kent Overstreet <kent.overstreet@...ux.dev>
> Cc: Pasha Tatashin <pasha.tatashin@...een.com>
> Cc: Roman Gushchin <roman.gushchin@...ux.dev>
> Cc: Shakeel Butt <shakeel.butt@...ux.dev>
> Cc: Sourav Panda <souravpanda@...gle.com>
> Cc: Suren Baghdasaryan <surenb@...gle.com>
> Cc: Usama Arif <usamaarif642@...il.com>
> Cc: Vlastimil Babka <vbabka@...e.cz>
> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
Perfect, Thanks!
> ---
>
> 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
> - 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.
>
> _
>
Powered by blists - more mailing lists