linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Ming Lin <mlin@kernel.org>, linux-mm@kvack.org
Cc: fengguang.wu@intel.com
Subject: Re: /proc/meminfo question
Date: Mon, 4 Apr 2016 17:31:45 +0200	[thread overview]
Message-ID: <570288E1.4060203@suse.cz> (raw)
In-Reply-To: <1459754566.19748.9.camel@kernel.org>

On 04/04/2016 09:22 AM, Ming Lin wrote:
> Hi,
>
> I'm debugging a memory leak in an internal driver.
> There is ~2G leak after stress tests.
>
> If I read below /proc/meminfo correctly, it doesn't show where the 2G
> memory is possibly used.
>
> Buffers + Cached + Active*/Inactive* + Slab* only about 300M.
>
> Is there other statistics not shown in /proc/meminfo or am I missing
> obvious things?

Nope. Statistics exist only for the common cases. Having e.g. each 
driver add own line there wouldn't be feasible.

However I already considered and would welcome an explicit 
"Unaccounted:" line in /prec/meminfo, so that the amount of possibly 
leaked memory is immediately visible and one doesn't need to remember 
which lines are best to sum up and whether there were subtle changes 
depending on kernel version.

> root@target:~# page-types
>               flags	page-count       MB  symbolic-flags			long-symbolic-flags

For debugging such leaks I suggest you try the page_owner functionality 
instead.

Vlastimil

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-04-04 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04  7:22 Ming Lin
2016-04-04 15:31 ` Vlastimil Babka [this message]
2016-04-04 23:26   ` Ming Lin

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=570288E1.4060203@suse.cz \
    --to=vbabka@suse.cz \
    --cc=fengguang.wu@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=mlin@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