From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: David Rientjes <rientjes@google.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Hartmut Beinlich <HBEINLIC@de.ibm.com>
Subject: Re: oom killer question
Date: Fri, 29 Oct 2010 14:34:09 -0700 [thread overview]
Message-ID: <1288388049.6872.263.camel@nimitz> (raw)
In-Reply-To: <20101029213004.GA2315@osiris.boeblingen.de.ibm.com>
On Fri, 2010-10-29 at 23:30 +0200, Heiko Carstens wrote:
>
> Looking only at slab_reclaimable I had the impression there _could_
> have been plenty of memory that could be reclaimed. Just wondering :)
Yeah, something funky is probably going on.
But, the "reclaimable" ones aren't guaranteed to be reclaimable. It
just means that we can usually reclaim most of them. If you have a
refcount leak on an object or something like that, they're effectively
unreclaimable still.
So, either way, the next step is to see which slab it was that blew up.
-- Dave
--
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:[~2010-10-29 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 12:14 oom killer question Heiko Carstens
2010-10-29 18:13 ` Dave Hansen
2010-10-29 21:30 ` Heiko Carstens
2010-10-29 21:34 ` Dave Hansen [this message]
2010-10-29 18:16 ` Andrew Morton
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=1288388049.6872.263.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=HBEINLIC@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--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).