linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Finding kernel RAM consumers ?
Date: Thu, 2 Jun 2022 21:11:00 +0100	[thread overview]
Message-ID: <YpkZVBQr5xk70Yxf@casper.infradead.org> (raw)
In-Reply-To: <70b4e1e46d9d63275a0dfe90f96f40ea14d89f0c.camel@infinera.com>

On Thu, Jun 02, 2022 at 07:24:23PM +0000, Joakim Tjernlund wrote:
> We have this small embedded target(aarch64) with 32 MB of RAM where the kernel consumes 14420K:
> Memory: 22444K/36864K available (3584K kernel code, 698K rwdata, 936K rodata, 320K init, 255K bss, 14420K reserved, 0K cma-reserved)
> 
> I want to track down were most of this RAM is consumed so I can trim away some MBs
> but I am having a hard time finding may way.
> Is there some tool/kernel config that can help me with that?

You may find this series of articles interesting:

https://lwn.net/Articles/741494/
https://lwn.net/Articles/744507/
https://lwn.net/Articles/746780/
https://lwn.net/Articles/748198/

While they're a little old and they're targetting a much smaller system
than yours, they may give you some ideas of things you can try and tools
you can use.


  reply	other threads:[~2022-06-02 20:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 19:24 Finding kernel RAM consumers ? Joakim Tjernlund
2022-06-02 20:11 ` Matthew Wilcox [this message]
2022-06-03  6:49   ` Joakim Tjernlund
2022-06-03 17:26     ` Joakim Tjernlund
2022-06-03 17:29       ` Matthew Wilcox
2022-06-03 18:11         ` Arnd Bergmann
2022-06-07  5:41           ` Alexander Dahl
2022-06-07  8:38             ` Arnd Bergmann
2022-06-07  8:54               ` Joakim Tjernlund
     [not found]               ` <Yp8d7NZ561/yr0HF@shell.armlinux.org.uk>
2022-06-07 10:22                 ` Arnd Bergmann

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=YpkZVBQr5xk70Yxf@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=Joakim.Tjernlund@infinera.com \
    --cc=linux-mm@kvack.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 NNTP newsgroup(s).