linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Subject: Re: Recent 3.x kernels: Memory leak causing OOMs
Date: Sun, 16 Feb 2014 14:17:44 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1402161406120.26926@chino.kir.corp.google.com> (raw)
In-Reply-To: <20140216200503.GN30257@n2100.arm.linux.org.uk>

On Sun, 16 Feb 2014, Russell King - ARM Linux wrote:

> Mem-info:
> Normal per-cpu:
> CPU    0: hi:   42, btch:   7 usd:  36
> active_anon:28041 inactive_anon:104 isolated_anon:0
>  active_file:11 inactive_file:11 isolated_file:0
>  unevictable:0 dirty:1 writeback:6 unstable:0
>  free:342 slab_reclaimable:170 slab_unreclaimable:570
>  mapped:13 shmem:139 pagetables:95 bounce:0
>  free_cma:0
> Normal free:1368kB min:1384kB low:1728kB high:2076kB active_anon:112164kB inactive_anon:416kB active_file:44kB inactive_file:44kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:131072kB managed:120152kB mlocked:0kB dirty:4kB
> writeback:24kB mapped:52kB shmem:556kB slab_reclaimable:680kB slab_unreclaimable:2280kB kernel_stack:248kB pagetables:380kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:136 all_unreclaimable? yes

All memory is accounted for here, there appears to be no leakage.

> [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
...
> [  756]     0   756    28163    27776      57        0             0 ld-linux.so.2

This is taking ~108MB of your ~117MB memory.

Three possibilies that immediately jump to mind:

 - if this is an SMP kernel, then too much free memory is being accounted
   for in cpu-0 vmstat differential and not returned to the ZVC pages 
   count,

 - there is a too little amount of "managed" memory attributed to 
   ZONE_NORMAL, the ~10MB difference between "present" and "managed"
   memory, or

 - ld-linux.so.2 is using too much memory.

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

  parent reply	other threads:[~2014-02-16 22:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16 20:05 Russell King - ARM Linux
2014-02-16 21:43 ` Theodore Ts'o
2014-02-17 18:34   ` Catalin Marinas
2014-02-16 22:17 ` David Rientjes [this message]
2014-02-16 22:50   ` Russell King - ARM Linux
2014-02-16 23:42     ` David Rientjes
2014-02-17 21:02     ` Maxime Bizon
2014-02-17 21:09       ` Russell King - ARM Linux
2014-03-15 10:19         ` Russell King - ARM Linux
2014-03-17  7:07           ` NeilBrown
2014-03-17  8:51             ` Russell King - ARM Linux
2014-03-17 18:18             ` Catalin Marinas
2014-03-17 19:33               ` Russell King - ARM Linux
2014-04-01  9:19                 ` Russell King - ARM Linux
2014-04-01 11:38                   ` Russell King - ARM Linux
2014-04-01 14:04                     ` Russell King - ARM Linux
2014-04-02 23:28                       ` NeilBrown
2014-04-01 15:58                     ` Catalin Marinas

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=alpine.DEB.2.02.1402161406120.26926@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@arm.linux.org.uk \
    /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