public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
	linux-parisc@vger.kernel.org
Subject: Re: Possible 6.5 regression: Huge values for "commited memory"
Date: Tue, 12 Sep 2023 21:32:28 +0200	[thread overview]
Message-ID: <db74e45c-aa0c-0256-96f2-07ebb936d57d@gmx.de> (raw)
In-Reply-To: <1694366957@msgid.manchmal.in-ulm.de>

Hi Christoph,

On 9/10/23 19:48, Christoph Biedl wrote:
> 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.

I doubt there is a specific memory leak in the parisc code.
Usually we just touch driver code or other arch-related code, so if
there is something wrong, then it must be in generic code and should
be visible on other platforms too.
We changed to the SLUB allocator, but I don't think this makes any
difference either.

Helge



  reply	other threads:[~2023-09-12 19:32 UTC|newest]

Thread overview: 12+ 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 [this message]
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=db74e45c-aa0c-0256-96f2-07ebb936d57d@gmx.de \
    --to=deller@gmx.de \
    --cc=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