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 23:04:03 +0300 [thread overview]
Message-ID: <84144f020710231304h6cba8626na4ab4bec0acda7a0@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710231227590.19626@schroedinger.engr.sgi.com>
Hi,
On Tue, 23 Oct 2007, Alexey Dobriyan wrote:
> > With SLAB this workload never went to OOM killer.
> > With SLUB and pretty much all debugging enabled, it finishes to the end
> > (albeit slowly).
> > With SLUB and no debugging, OOM killer kicks in.
On 10/23/07, Christoph Lameter <clameter@sgi.com> wrote:
> Not sure what this is. Maybe the slowing SLUB solves the race.
What kind of race are you thinking of? What I initially thought was
that the problem is that SLUB messes up some other VM heuristics due
to different object sizes, not holding on to empty slabs, and/or page
allocator pass-through. I guess only object size is affected by
debugging, though?
next prev parent reply other threads:[~2007-10-23 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 18:16 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
2007-10-25 2:43 ` Christoph Lameter
2007-10-25 3:06 ` Nick Piggin
2007-10-23 20:04 ` Pekka Enberg [this message]
2007-10-23 20:09 ` Christoph Lameter
2007-10-23 20:41 ` Pekka Enberg
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=84144f020710231304h6cba8626na4ab4bec0acda7a0@mail.gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®