From: David Rientjes <rientjes@google.com>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Christoph Lameter <cl@linux.com>, Michal Hocko <mhocko@suse.cz>,
Han Pingtian <hanpt@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org
Subject: Re: OOM-killer and strange RSS value in 3.9-rc7
Date: Tue, 21 Jan 2014 14:12:45 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1401211411140.1666@chino.kir.corp.google.com> (raw)
In-Reply-To: <52caac5c.27cb440a.533d.ffffbbd2SMTPIN_ADDED_BROKEN@mx.google.com>
On Mon, 6 Jan 2014, Wanpeng Li wrote:
> >Is there any progress against slub's fix?
> >
> >MemTotal: 7760960 kB
> >Slab: 7064448 kB
> >SReclaimable: 143936 kB
> >SUnreclaim: 6920512 kB
> >
> >112084 10550 9% 16.00K 3507 32 1795584K kmalloc-16384
> >2497920 48092 1% 0.50K 19515 128 1248960K kmalloc-512
> >6058888 89363 1% 0.19K 17768 341 1137152K kmalloc-192
> >114468 13719 11% 4.58K 2082 55 532992K task_struct
> >
>
> This machine has 200 CPUs and 8G memory. There is an oom storm, we are
> seeing OOM even in boot process.
>
Is this still a problem with 3.9 and later kernels? Please try to
reproduce it on 3.13.
If it does reproduce, could you try to pinpoint the problem with kmemleak?
Look into Documentation/kmemleak.txt which should identify where these
leaks are coming from with your slab allocator of choice.
--
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>
next prev parent reply other threads:[~2014-01-21 22:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1304161315290.30779@chino.kir.corp.google.com>
[not found] ` <20130417094750.GB2672@localhost.localdomain>
[not found] ` <20130417141909.GA24912@dhcp22.suse.cz>
[not found] ` <20130418101541.GC2672@localhost.localdomain>
[not found] ` <20130418175513.GA12581@dhcp22.suse.cz>
[not found] ` <20130423131558.GH8001@dhcp22.suse.cz>
[not found] ` <20130424044848.GI2672@localhost.localdomain>
2013-04-24 9:47 ` Michal Hocko
2013-04-24 15:36 ` Christoph Lameter
2013-04-25 6:07 ` Han Pingtian
2013-04-25 17:17 ` Christoph Lameter
2013-04-27 8:20 ` Will Huck
2013-04-29 14:49 ` Christoph Lameter
2013-05-01 3:13 ` Will Huck
2013-05-02 15:10 ` Christoph Lameter
2013-05-09 13:17 ` Will Huck
2013-05-09 14:00 ` Christoph Lameter
2013-05-10 0:42 ` Will Huck
2013-05-10 16:00 ` Christoph Lameter
2013-04-25 18:24 ` Christoph Lameter
2013-04-26 6:24 ` Han Pingtian
2013-04-26 14:42 ` Christoph Lameter
2013-04-27 11:24 ` Han Pingtian
2013-04-29 14:50 ` Christoph Lameter
2013-04-29 14:57 ` Michal Hocko
2013-05-02 10:56 ` Han Pingtian
2013-05-02 15:10 ` Christoph Lameter
2013-05-03 3:03 ` Han Pingtian
2013-05-03 15:25 ` Christoph Lameter
2013-05-03 15:34 ` Michal Hocko
2013-05-03 16:16 ` Christoph Lameter
2013-12-27 10:39 ` Wanpeng Li
2014-01-06 13:15 ` Wanpeng Li
[not found] ` <52caac5c.27cb440a.533d.ffffbbd2SMTPIN_ADDED_BROKEN@mx.google.com>
2014-01-21 22:12 ` David Rientjes [this message]
2014-01-22 23:45 ` Wanpeng Li
2013-04-25 5:41 ` Han Pingtian
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.1401211411140.1666@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=cl@linux.com \
--cc=hanpt@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=mhocko@suse.cz \
--cc=penberg@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