From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Christoph Lameter <clameter@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
mingo@elte.hu
Subject: Re: tbench regression - Why process scheduler has impact on tbench and why small per-cpu slab (SLUB) cache creates the scenario?
Date: Mon, 10 Sep 2007 08:10:45 +1000 [thread overview]
Message-ID: <200709100810.46341.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <1189385792.14611.1.camel@ymzhang>
On Monday 10 September 2007 10:56, Zhang, Yanmin wrote:
> On Sat, 2007-09-08 at 18:08 +1000, Nick Piggin wrote:
> > On Wednesday 05 September 2007 17:07, Christoph Lameter wrote:
> > > On Wed, 5 Sep 2007, Zhang, Yanmin wrote:
> > > > > slub_max_order=3 slub_min_objects=8
> > > >
> > > > I tried this approach. The testing result showed 2.6.23-rc4 is about
> > > > 2.5% better than 2.6.22. It really resovles the issue.
> > >
> > > Note also that the configuration you tried is the way SLUB is
> > > configured in Andrew's tree.
> >
> > It still doesn't sound like it is competitive with SLAB at the same
> > sizes. What's the problem?
>
> Process scheduler and small SLUB per-cpu cache work together to create the
> tebnch regression.
OK, so after isolating the scheduler, then SLUB should be as fast as SLAB
at the same allocation size. That's basically what we need to do before we
can replace SLAB with it, I think?
next prev parent reply other threads:[~2007-09-10 13:52 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 [this message]
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
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=200709100810.46341.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=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox