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 <linux-mm@kvack.org>
Subject: Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds)
Date: Tue, 23 Oct 2007 23:41:42 +0300 [thread overview]
Message-ID: <84144f020710231341p189435b1y5514e5be981b9b1c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710231305050.20095@schroedinger.engr.sgi.com>
Hi Christoph,
(I fixed linux-mm cc to kvack.org.)
On 10/23/07, Christoph Lameter <clameter@sgi.com> wrote:
> The number of objects per page is reduced by enabling full debugging. That
> triggers a potential of more order 1 allocations but we are failing at
> order 0 allocs.
Yeah, but we're _not failing_ when debugging is enabled. Thus, it's
likely, that the _failing_ (non-debug) case has potential for more
order 0 allocs, no? I am just guessing here but maybe it's
slab_order() behaving differently from calculate_slab_order() so that
we see more order 0 pressure in SLUB than SLAB?
Pekka
--
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 parent reply other threads:[~2007-10-23 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071023181615.GA10377@martell.zuzino.mipt.ru>
[not found] ` <Pine.LNX.4.64.0710231227590.19626@schroedinger.engr.sgi.com>
[not found] ` <84144f020710231304h6cba8626na4ab4bec0acda7a0@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0710231305050.20095@schroedinger.engr.sgi.com>
2007-10-23 20:41 ` Pekka Enberg [this message]
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=84144f020710231341p189435b1y5514e5be981b9b1c@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@kvack.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