All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <clameter@sgi.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org
Subject: Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds)
Date: Tue, 23 Oct 2007 22:48:49 +0300	[thread overview]
Message-ID: <471E5021.8090300@cs.helsinki.fi> (raw)
In-Reply-To: <Pine.LNX.4.64.0710231227590.19626@schroedinger.engr.sgi.com>

Hi,

On Tue, 23 Oct 2007, Alexey Dobriyan wrote:
> > cc1 invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0

Christoph Lameter wrote:
> Regular Order 0 alloc .... but why is there no memory available , 
> reclaimed?

I am too wondering where all that memory is going. Logging /proc/meminfo 
and slabinfo -S (see Documentation/vm/slabinfo.c) every few minutes or 
so probably might help answering that question.

				Pekka


  reply	other threads:[~2007-10-23 19:49 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 [this message]
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
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=471E5021.8090300@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=adobriyan@gmail.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@vger.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 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.