From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: linux-parisc@vger.kernel.org
Subject: Possible 6.5 regression: Huge values for "commited memory"
Date: Sun, 10 Sep 2023 19:48:23 +0200 [thread overview]
Message-ID: <1694366957@msgid.manchmal.in-ulm.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Hello,
For the time being, just an observation: I monitor various parameters on
my systems, and among them is "Committed memory", the Committed_AS value
in /proc/meminfo.
Since upgrading to the 6.5.x series, I noticed the value there grows way
higher values then previously in hppa, even if the machine is idle.
Values seem to rise up to around 1.6 Gbyte, long-term average is rather
200-300 Mbyte. Also, I cannot see any memory hogs in top. The workload
hasn't changed in months.
To sum it up, I reckon something went wrong in the memory usage
accounting. Is this already on radar, or should I start bisecting? That
might take a lot of time, though.
Christoph
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-09-10 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 17:48 Christoph Biedl [this message]
2023-09-12 19:32 ` Possible 6.5 regression: Huge values for "commited memory" Helge Deller
2023-09-13 0:25 ` Bagas Sanjaya
2023-09-15 16:27 ` Michael Labiuk
[not found] ` <ZQWUzwiKWLk79qbp@debian.me>
2023-09-16 19:31 ` Linus Torvalds
2023-09-16 21:17 ` Linus Torvalds
2023-09-16 22:20 ` Michael Labiuk
2023-09-16 22:25 ` Linus Torvalds
2023-09-17 5:02 ` Helge Deller
2023-09-17 6:10 ` Greg Kroah-Hartman
2023-09-21 7:09 ` Christoph Biedl
2023-09-16 22:35 ` Liam R. Howlett
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=1694366957@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=linux-parisc@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).