linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 07 May 2007 17:40:34 -0700	[thread overview]
Message-ID: <1178584834.15701.18.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0705041800070.28492@schroedinger.engr.sgi.com>

On Fri, 2007-05-04 at 18:02 -0700, Christoph Lameter wrote:
> On Fri, 4 May 2007, Tim Chen wrote:
> 
> > On Thu, 2007-05-03 at 18:45 -0700, Christoph Lameter wrote:
> > > Hmmmm.. One potential issues are the complicated way the slab is 
> > > handled. Could you try this patch and see what impact it has?
> > > 
> > The patch boost the throughput of TCP_STREAM test by 5%, for both slab
> > and slub.  But slab is still 5% better in my tests.
> 
> Really? buffer head handling improves TCP performance? I think you have 
> run to run variances. I need to look at this myself.

I think the object of interest should be sk_buff, not buffer_head. I
made a mistake of accidentally using another config after applying your
buffer head patch.  I compared the kernel again under the same config,
with and without the buffer_head patch. There's no boost to TCP_STREAM
test from the patch.  So things make sense again.  My apology for the
error. 

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.

Thanks.

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>

  reply	other threads:[~2007-05-08  0:40 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 [this message]
2007-05-08  1:49             ` Christoph Lameter
2007-05-08 21:02               ` Tim Chen
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=1178584834.15701.18.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