From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
mingo@elte.hu, Mel Gorman <mel@skynet.ie>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: tbench regression - Why process scheduler has impact on tbench and why small per-cpu slab (SLUB) cache creates the scenario?
Date: Tue, 11 Sep 2007 14:59:09 +1000 [thread overview]
Message-ID: <200709111459.10148.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0709111314190.25781@schroedinger.engr.sgi.com>
On Wednesday 12 September 2007 06:19, Christoph Lameter wrote:
> On Tue, 11 Sep 2007, Nick Piggin wrote:
> > The impression I got at vm meeting was that SLUB was good to go :(
>
> Its not? I have had Intel test this thoroughly and they assured me that it
> is up to SLAB. This particular case is an synthetic tests for a PAGE_SIZE
> alloc and SLUB was not optimized for that case because PAGE_SIZEd
> allocations should be handled by the page allocators. Quicklists were
> introduced for the explicit purpose to get these messy page sized cases
> out of the slab allocators.
I heard from one person at KS and one person here that it is not. If they're
simply missing some patch that's in -mm, and there is no longer a SLUB vs
SLAB regression when using equivalent page allocation order, then that's
fine.
next prev parent reply other threads:[~2007-09-11 20:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 0:46 tbench regression - Why process scheduler has impact on tbench and why small per-cpu slab (SLUB) cache creates the scenario? Zhang, Yanmin
2007-09-05 3:59 ` Christoph Lameter
2007-09-05 5:22 ` Zhang, Yanmin
2007-09-05 6:58 ` Christoph Lameter
2007-09-05 9:13 ` Zhang, Yanmin
2007-09-05 10:45 ` Christoph Lameter
2007-09-06 0:52 ` Zhang, Yanmin
2007-09-05 7:07 ` Christoph Lameter
2007-09-08 8:08 ` Nick Piggin
2007-09-10 0:56 ` Zhang, Yanmin
2007-09-09 22:10 ` Nick Piggin
2007-09-10 19:07 ` Christoph Lameter
2007-09-10 15:17 ` Nick Piggin
2007-09-11 20:19 ` Christoph Lameter
2007-09-11 4:59 ` Nick Piggin [this message]
2007-09-13 6:04 ` Siddha, Suresh B
2007-09-13 18:03 ` Christoph Lameter
2007-09-14 19:15 ` Siddha, Suresh B
2007-09-14 19:51 ` Christoph Lameter
2007-09-19 2:17 ` Siddha, Suresh B
2007-09-20 17:53 ` 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=200709111459.10148.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@skynet.ie \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=yanmin_zhang@linux.intel.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 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.