linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3.4-rc4 oom killer out of control.
Date: Thu, 26 Apr 2012 18:54:21 -0400	[thread overview]
Message-ID: <20120426225421.GB13598@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204261547250.15785@chino.kir.corp.google.com>

On Thu, Apr 26, 2012 at 03:49:06PM -0700, David Rientjes wrote:
 > On Thu, 26 Apr 2012, Dave Jones wrote:
 > 
 > > Disabling it stops it hogging the cpu obviously, but there's still 8G of RAM
 > > and 1G of used swap sitting around doing something.
 > > 
 > 
 > Right, I eluded to this in another email because the rss sizes from your 
 > oom log weren't necessarily impressive.  Could you post the output of 
 > /proc/meminfo?

MemTotal:        8149440 kB
MemFree:          142560 kB
Buffers:            1408 kB
Cached:            11504 kB
SwapCached:         9336 kB
Active:          6124932 kB
Inactive:        1232176 kB
Active(anon):    6119160 kB
Inactive(anon):  1225228 kB
Active(file):       5772 kB
Inactive(file):     6948 kB
Unevictable:        5656 kB
Mlocked:            5656 kB
SwapTotal:       1423736 kB
SwapFree:         343596 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:       7341364 kB
Mapped:             5720 kB
Shmem:               192 kB
Slab:             267408 kB
SReclaimable:      40808 kB
SUnreclaim:       226600 kB
KernelStack:        3280 kB
PageTables:       183104 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     5498456 kB
Committed_AS:   111294188 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      346720 kB
VmallocChunk:   34359384056 kB
HardwareCorrupted:     0 kB
AnonHugePages:         0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:       98344 kB
DirectMap2M:     8288256 kB


--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-04-26 22:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 19:35 3.4-rc4 oom killer out of control Dave Jones
2012-04-26 20:53 ` Dave Jones
2012-04-26 22:30   ` David Rientjes
2012-04-26 21:40 ` David Rientjes
2012-04-26 21:52   ` Dave Jones
2012-04-26 22:20     ` David Rientjes
2012-04-26 22:44       ` Dave Jones
2012-04-26 22:49         ` David Rientjes
2012-04-26 22:54           ` Dave Jones [this message]
2012-04-27  0:54         ` Steven Rostedt
2012-04-27  2:02           ` Dave Jones
2012-05-03 22:14   ` David Rientjes
2012-05-03 22:29     ` Dave Jones
2012-05-17 21:33       ` [patch] mm, oom: normalize oom scores to oom_score_adj scale only for userspace David Rientjes
2012-05-17 21:50         ` Andrew Morton
2012-05-23  7:15           ` [patch v2] " David Rientjes
2012-05-23 22:37             ` Andrew Morton
2012-05-24  6:02               ` David Rientjes

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=20120426225421.GB13598@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    /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).