linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "willy@infradead.org" <willy@infradead.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Finding kernel RAM consumers ?
Date: Fri, 3 Jun 2022 06:49:03 +0000	[thread overview]
Message-ID: <88dfec5a1c98f4eb71e23cafe89db4395ea12811.camel@infinera.com> (raw)
In-Reply-To: <YpkZVBQr5xk70Yxf@casper.infradead.org>

On Thu, 2022-06-02 at 21:11 +0100, Matthew Wilcox wrote:
> 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flwn.net%2FArticles%2F741494%2F&amp;data=05%7C01%7CJoakim.Tjernlund%40infinera.com%7C509eaa2f688b4612945208da44d40494%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637897974658412129%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=zP2oazSeoVKiTrbPONqmQXEhzyIIL3pQdvsKfN8nOA0%3D&amp;reserved=0
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flwn.net%2FArticles%2F744507%2F&amp;data=05%7C01%7CJoakim.Tjernlund%40infinera.com%7C509eaa2f688b4612945208da44d40494%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637897974658412129%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=9kNmXDhuQ24tWlECGrYQOqaaTsc0sOO4TozcQBk5aYc%3D&amp;reserved=0
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flwn.net%2FArticles%2F746780%2F&amp;data=05%7C01%7CJoakim.Tjernlund%40infinera.com%7C509eaa2f688b4612945208da44d40494%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637897974658412129%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=ZFu0q4tXX677JwkgBqK73M8WxDrhylw0XnuEw5Y8mA4%3D&amp;reserved=0
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flwn.net%2FArticles%2F748198%2F&amp;data=05%7C01%7CJoakim.Tjernlund%40infinera.com%7C509eaa2f688b4612945208da44d40494%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637897974658412129%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=ws5Rlrhts80ndzr8aEv3xTu6EmCnND3L%2FmGXHLDaygw%3D&amp;reserved=0
> 
> 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.

Those are interesting, thanks.
In my case it is the amount of work space RAM allocated that is a bit much. The kernel code/data
is 5+MB but the total need is 14MB, 9MB is buffer and similar.

 Jocke

  reply	other threads:[~2022-06-03  6:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 19:24 Joakim Tjernlund
2022-06-02 20:11 ` Matthew Wilcox
2022-06-03  6:49   ` Joakim Tjernlund [this message]
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=88dfec5a1c98f4eb71e23cafe89db4395ea12811.camel@infinera.com \
    --to=joakim.tjernlund@infinera.com \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.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