From: Mel Gorman <mel@csn.ul.ie>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, Marcelo Tosatti <marcelo@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
mpm@selenic.com, Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [SLUB 0/3] SLUB: The unqueued slab allocator V4
Date: Fri, 9 Mar 2007 14:00:05 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703091355520.16052@skynet.skynet.ie> (raw)
In-Reply-To: <Pine.LNX.4.64.0703081135280.3130@schroedinger.engr.sgi.com>
On Thu, 8 Mar 2007, Christoph Lameter wrote:
> Note that I am amazed that the kernbench even worked. On small machine
How small? The machines I am testing on aren't "big" but they aren't
misterable either.
> I
> seem to be getting into trouble with order 1 allocations.
That in itself is pretty incredible. From what I see, allocations up to 3
generally work unless they are atomic even with the vanilla kernel. That
said, it could be because slab is holding onto the high order pages for
itself.
> SLAB seems to be
> able to avoid the situation by keeping higher order pages on a freelist
> and reduce the alloc/frees of higher order pages that the page allocator
> has to deal with. Maybe we need per order queues in the page allocator?
>
I'm not sure what you mean by per-order queues. The buddy allocator
already has per-order lists.
> There must be something fundamentally wrong in the page allocator if the
> SLAB queues fix this issue. I was able to fix the issue in V5 by forcing
> SLUB to keep a mininum number of objects around regardless of the fit to
> a page order page. Pass through is deadly since the crappy page allocator
> cannot handle it.
>
> Higher order page allocation failures can be avoided by using kmalloc.
> Yuck! Hopefully your patches fix that fundamental problem.
>
One way to find out for sure.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2007-03-09 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 2:35 Christoph Lameter
2007-03-07 2:35 ` [SLUB 1/3] SLUB core Christoph Lameter
2007-03-07 2:35 ` [SLUB 2/3] Large kmalloc pass through. Removal of large general slabs Christoph Lameter
2007-03-07 2:40 ` Matt Mackall
2007-03-07 3:22 ` Christoph Lameter
2007-03-07 9:01 ` Peter Zijlstra
2007-03-07 15:34 ` Christoph Lameter
2007-03-07 18:03 ` Matt Mackall
2007-03-07 18:23 ` Christoph Lameter
2007-03-07 2:35 ` [SLUB 3/3] Guarantee minimum number of objects in a slab Christoph Lameter
2007-03-08 10:54 ` [SLUB 0/3] SLUB: The unqueued slab allocator V4 Mel Gorman
2007-03-08 16:48 ` Christoph Lameter
2007-03-08 17:40 ` Mel Gorman
2007-03-08 18:16 ` Christoph Lameter
2007-03-09 13:55 ` Mel Gorman
2007-03-08 21:54 ` Christoph Lameter
2007-03-09 14:00 ` Mel Gorman [this message]
2007-03-09 16:40 ` Christoph Lameter
2007-03-09 15:06 ` Mel Gorman
2007-03-09 17:21 ` Christoph Lameter
2007-03-08 17:46 ` 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=Pine.LNX.4.64.0703091355520.16052@skynet.skynet.ie \
--to=mel@csn.ul.ie \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=marcelo@kvack.org \
--cc=mpm@selenic.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