From: Christoph Lameter <clameter@sgi.com>
To: Mel Gorman <mel@csn.ul.ie>
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 09:21:00 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703090907330.7315@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703091503580.16052@skynet.skynet.ie>
On Fri, 9 Mar 2007, Mel Gorman wrote:
> The results without slub_debug were not good except for IA64. x86_64 and ppc64
> both blew up for a variety of reasons. The IA64 results were
Yuck that is the dst issue that Adrian is also looking at. Likely an issue
with slab merging and RCU frees.
> KernBench Comparison
> --------------------
> 2.6.21-rc2-mm2-clean 2.6.21-rc2-mm2-slub
> %diff
> User CPU time 1084.64 1032.93 4.77%
> System CPU time 73.38 63.14 13.95%
> Total CPU time 1158.02 1096.07 5.35%
> Elapsed time 307.00 285.62 6.96%
Wow! The first indication that we are on the right track with this.
> AIM9 Comparison
> 2 page_test 2097119.26 3398259.27 1301140.01 62.04% System Allocations & Pages/second
Wow! Must have all stayed within slab boundaries.
> 8 link_test 64776.04 7488.13 -57287.91 -88.44% Link/Unlink Pairs/second
Crap. Maybe we straddled a slab boundary here?
next prev parent reply other threads:[~2007-03-09 17:21 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
2007-03-09 16:40 ` Christoph Lameter
2007-03-09 15:06 ` Mel Gorman
2007-03-09 17:21 ` Christoph Lameter [this message]
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.0703090907330.7315@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=marcelo@kvack.org \
--cc=mel@csn.ul.ie \
--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
all inboxes | Powered by JetHome®