From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
"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>,
Matthew.R.wilcox@intel.com
Subject: Re: tbench regression - Why process scheduler has impact on tbench and why small per-cpu slab (SLUB) cache creates the scenario?
Date: Tue, 18 Sep 2007 19:17:05 -0700 [thread overview]
Message-ID: <20070919021705.GB20863@linux-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709141242200.17369@schroedinger.engr.sgi.com>
On Fri, Sep 14, 2007 at 12:51:34PM -0700, Christoph Lameter wrote:
> On Fri, 14 Sep 2007, Siddha, Suresh B wrote:
> > We are trying to get the latest data with 2.6.23-rc4-mm1 with and without
> > slub. Is this good enough?
>
> Good enough. If you are concerned about the page allocator pass through
> then you may want to test the page allocator pass through patchset
> separately. The fastpath of the page allocator is currently not
> competitive if you always free and allocate a single page. If contiguous
> pages are allocated then the pass through is superior.
We are having all sorts of stability issues with -mm kernels, let alone
perf testing :(
For now, we are trying to do slab Vs slub comparisons for the mainline kernels.
Let's see how that goes.
Meanwhile, any chance that you can point us at relevant recent patches/fixes
that are in -mm and perhaps that can be applied to mainline kernel?
thanks,
suresh
next prev parent reply other threads:[~2007-09-19 2:17 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
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 [this message]
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=20070919021705.GB20863@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=Matthew.R.wilcox@intel.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@skynet.ie \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox