From: David Wang <00107082@163.com>
To: kent.overstreet@linux.dev, surenb@google.com, keescook@chromium.org
Cc: linux-kernel@vger.kernel.org
Subject: [BUG?] memory allocation profiling: the counters are not non-decreasing.
Date: Wed, 5 Jun 2024 20:37:10 +0800 [thread overview]
Message-ID: <20240605123710.7396-1-00107082@163.com> (raw)
Hi,
I was playing with this new feature of memory allocation profiling, when I plot the data, grouped by caller's source dir,
I noticed that the counters are not non-decreasing.
If I understand this feature correctly, all counters should be non-decreasing, right?
Or is there some TTL for stale items?
Following is a simpler script demonstrating my sayings
$ for i in {1..100}; do sudo cat /proc/allocinfo | grep " mm\/" | awk '{s+=$2}END{print s}'; sleep 10; done
1194453
1196935
1198957
1199716
1200770
1190795 <--- decrease here
1192702
1193070
1193812
1195069
1196491
...
FYI
David
next reply other threads:[~2024-06-05 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 12:37 David Wang [this message]
2024-06-05 20:00 ` Suren Baghdasaryan
2024-06-06 3:42 ` David Wang
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=20240605123710.7396-1-00107082@163.com \
--to=00107082@163.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=surenb@google.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
all inboxes | Powered by JetHome®