[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250916160110.266190-1-surenb@google.com>
Date: Tue, 16 Sep 2025 09:01:10 -0700
From: Suren Baghdasaryan <surenb@...gle.com>
To: akpm@...ux-foundation.org
Cc: kent.overstreet@...ux.dev, vbabka@...e.cz, hannes@...xchg.org,
usamaarif642@...il.com, 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,
surenb@...gle.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: [PATCH 1/1] fixup: alloc_tag: mark inaccurate allocation counters in
/proc/allocinfo output
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
+ 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.
+
Example output.
::
base-commit: 199236646ffd82b5a5bcf2bca1579ea06cb0ae74
--
2.51.0.384.g4c02a37b29-goog
Powered by blists - more mailing lists