From: Michal Hocko <mhocko@suse.cz>
To: Christoph Lameter <cl@linux.com>
Cc: Han Pingtian <hanpt@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
penberg@kernel.org, rientjes@google.com, linux-mm@kvack.org
Subject: Re: OOM-killer and strange RSS value in 3.9-rc7
Date: Fri, 3 May 2013 17:34:50 +0200 [thread overview]
Message-ID: <20130503153450.GA18709@dhcp22.suse.cz> (raw)
In-Reply-To: <0000013e6aff6f95-b8fa366e-51a5-4632-962e-1b990520f5a8-000000@email.amazonses.com>
On Fri 03-05-13 15:25:25, Christoph Lameter wrote:
> On Fri, 3 May 2013, Han Pingtian wrote:
>
> > On Thu, May 02, 2013 at 03:10:15PM +0000, Christoph Lameter wrote:
> > > On Thu, 2 May 2013, Han Pingtian wrote:
> > >
> > > > Looks like "ibmvscsi" + "slub" can trigger this problem.
> > >
> > > And the next merge of the slab-next tree will also cause SLAB to trigger
> > > this issue. I would like to have this fixes. The slab allocator purpose is
> > > to servr objects that are a fraction of a page and not objects that are
> > > larger than the maximum allowed sizes of the page allocator.
> >
> > So the problem is in memory management code, not in ibmvscis? And looks
> > like there is a fix already?
>
> Both should be fixed.
Could you point to the specific commit(s), please?
> Making requests for large amounts of memory from an allocator that is
> supposed to hand out fraction of a page does not make sense.
AFAIR there were lots of objects in size-512 as well.
--
Michal Hocko
SUSE Labs
--
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:[~2013-05-03 15:34 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 [this message]
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
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=20130503153450.GA18709@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=cl@linux.com \
--cc=hanpt@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.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