linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Tim Chen <tim.c.chen@linux.intel.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, 7 May 2007 21:57:32 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705072150490.4939@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1178584834.15701.18.camel@localhost.localdomain>

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.

If this is cache miss related then a larger page order may take are 
of this. Boot with (assume you got 2.6.21-mm1 at least...)

slub_min_order=6 slub_max_order=7

which will give you an allocation unit of 256k. Just tried it. It 
actually works but has no effect here whatsoever on UP netperf 
performance. netperf performance dropped from 6MB(slab)/6.2MB(slub) on 
2.6.21-rc7-mm1 to 4.5MB (both) on 2.6.21-mm1. So I guess there is 
something also going on with the networking layer.

Still have not found a machine here where I could repeat your 
results.

--
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>

  parent reply	other threads:[~2007-05-08  4:57 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
2007-05-08 22:02                 ` Christoph Lameter
2007-05-08  4:57             ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0705072150490.4939@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=arjan@infradead.org \
    --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=tim.c.chen@linux.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