From: Tim Chen <tim.c.chen@linux.intel.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: "Chen, Tim C" <tim.c.chen@intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"Zhang, Yanmin" <yanmin.zhang@intel.com>,
"Wang, Peter Xihong" <peter.xihong.wang@intel.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: RE: Regression with SLUB on Netperf and Volanomark
Date: Tue, 08 May 2007 14:02:04 -0700 [thread overview]
Message-ID: <1178658124.15701.35.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0705071848300.1378@schroedinger.engr.sgi.com>
On Mon, 2007-05-07 at 18:49 -0700, Christoph Lameter wrote:
> On Mon, 7 May 2007, Tim Chen wrote:
>
> > However, the output from TCP_STREAM is quite stable.
> > I am still seeing a 4% difference between the SLAB and SLUB kernel.
> > Looking at the L2 cache miss rate with emon, I saw 6% more cache miss on
> > the client side with SLUB. The server side has the same amount of cache
> > miss. This is test under SMP mode with client and server bound to
> > different core on separate package.
>
> Could you try the following patch on top of 2.6.21-mm1 with the patches
> from http://ftp.kernel.org/pub/linux/kernel/people/christoph/slub-patches?
>
> I sent it to you before. This is one is an updated version
>
>
>
> Avoid atomic overhead in slab_alloc and slab_free
>
I tried the slub-patches and the avoid atomic overhead patch against
2.6.21-mm1. It brings the TCP_STREAM performance for SLUB to the SLAB
level. The patches not mentioned in the "series" file did not apply
cleanly to 2.6.21-mm1 and I skipped most of those.
Patches applied are:
http://ftp.kernel.org/pub/linux/kernel/people/christoph/slub-
patches/series + dentry_target_reclaimed + kmem_cache_ops + slub_stats +
skip_atomic_overhead
Without skip atomic overhead patch, the throughput drops by 1 to 1.5%.
The change from slub_min_order=0 slub_max_order=4
to slub_min_order=6 slub_max_order=7 did not make much difference in
my tests.
Tim
--
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-05-08 21:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 18:43 Tim Chen
2007-05-02 19:47 ` Christoph Lameter
2007-05-03 23:28 ` Chen, Tim C
2007-05-04 0:44 ` Christoph Lameter
2007-05-04 1:45 ` Christoph Lameter
2007-05-04 23:41 ` Tim Chen
2007-05-05 1:02 ` Christoph Lameter
2007-05-08 0:40 ` Tim Chen
2007-05-08 1:49 ` Christoph Lameter
2007-05-08 21:02 ` Tim Chen [this message]
2007-05-08 22:02 ` Christoph Lameter
2007-05-08 4:57 ` Christoph Lameter
2007-05-04 2:42 ` Christoph Lameter
2007-05-04 17:14 ` Tim Chen
2007-05-04 18:10 ` Christoph Lameter
2007-05-04 17:39 ` Tim Chen
2007-05-04 18:27 ` Christoph Lameter
2007-05-04 22:43 ` Tim Chen
2007-05-04 23:59 ` Christoph Lameter
2007-05-04 23:42 ` Tim Chen
2007-05-05 1:41 ` Christoph Lameter
2007-05-05 2:05 ` 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=1178658124.15701.35.camel@localhost.localdomain \
--to=tim.c.chen@linux.intel.com \
--cc=arjan@infradead.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peter.xihong.wang@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=tim.c.chen@intel.com \
--cc=yanmin.zhang@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