All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
	Linux PARISC <linux-parisc@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Possible 6.5 regression: Huge values for "commited memory"
Date: Wed, 13 Sep 2023 07:25:54 +0700	[thread overview]
Message-ID: <ZQEBkjSgdXSOMq3t@debian.me> (raw)
In-Reply-To: <1694366957@msgid.manchmal.in-ulm.de>

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

On Sun, Sep 10, 2023 at 07:48:23PM +0200, Christoph Biedl wrote:
> 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.

Upgrading from what version?

Also, can you describe your setup? And what is the value of `Committed_AS`
on the kernel before you upgrade? (Hint: paste full /proc/meminfo from
both old and new kernel.)

> 
> 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.
> 

You can certainly do bisection (see Documentation/admin-guide/bug-bisect.rst
in the kernel sources for how to do that).

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2023-09-13  0:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 17:48 Possible 6.5 regression: Huge values for "commited memory" Christoph Biedl
2023-09-12 19:32 ` Helge Deller
2023-09-13  0:25 ` Bagas Sanjaya [this message]
2023-09-15 16:27   ` Michael Labiuk
2023-09-16 11:43 ` Bagas Sanjaya
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
2023-09-17 10:13   ` Bagas Sanjaya

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=ZQEBkjSgdXSOMq3t@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.