From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>, Mel Gorman <mel@skynet.ie>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org
Subject: Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds)
Date: Thu, 25 Oct 2007 12:34:01 +1000 [thread overview]
Message-ID: <200710251234.01440.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0710241913220.29434@schroedinger.engr.sgi.com>
On Thursday 25 October 2007 12:15, Christoph Lameter wrote:
> On Wed, 24 Oct 2007, Alexey Dobriyan wrote:
> > [12728.701398] DMA free:8032kB min:32kB low:40kB high:48kB active:2716kB
> > inactive:2208kB present:12744kB pages_scanned:9299 all_unreclaimable?
> > yes [12728.701567] lowmem_reserve[]: 0 2003 2003 2003 [12728.701654]
>
> Ummm... all unreclaimable is set! Are you mlocking the pages in memory? Or
> what causes this? All pages under writeback? What is the dirty ratio set
> to?
Why is SLUB behaving differently, though.
Memory efficiency wouldn't be the reason, would it? I mean, SLUB
should be more efficient than SLAB, plus have less data lying around
in queues.
next prev parent reply other threads:[~2007-10-25 2:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 18:16 SLUB 0:1 SLAB (OOM during massive parallel kernel builds) Alexey Dobriyan
2007-10-23 19:35 ` Christoph Lameter
2007-10-23 19:48 ` Pekka Enberg
2007-10-23 19:57 ` Christoph Lameter
2007-10-24 8:09 ` Mel Gorman
2007-10-24 19:28 ` Alexey Dobriyan
2007-10-25 2:15 ` Christoph Lameter
2007-10-25 2:34 ` Nick Piggin [this message]
2007-10-25 2:43 ` Christoph Lameter
2007-10-25 3:06 ` Nick Piggin
2007-10-23 20:04 ` Pekka Enberg
2007-10-23 20:09 ` Christoph Lameter
2007-10-23 20:41 ` Pekka Enberg
2007-10-23 20:41 ` Pekka Enberg
2007-10-24 16:56 ` Christoph Lameter
2007-10-24 16:56 ` Christoph Lameter
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=200710251234.01440.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=adobriyan@gmail.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=mel@skynet.ie \
--cc=penberg@cs.helsinki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.