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: suresh.b.siddha@intel.com, yanmin.zhang@intel.com,
	peter.xihong.wang@intel.com, arjan.van.de.ven@intel.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Regression with SLUB on Netperf and Volanomark
Date: Wed, 2 May 2007 12:47:33 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705021243480.1543@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1178131409.23795.160.camel@localhost.localdomain>

On Wed, 2 May 2007, Tim Chen wrote:

> We tested SLUB on a 2 socket Clovertown (Core 2 cpu with 2 cores/socket)
> and a 2 socket Woodcrest (Core2 cpu with 4 cores/socket).  

Try to boot with

slub_max_order=4 slub_min_objects=8

If that does not help increase slub_min_objects to 16.

> We found that for Netperf's TCP streaming tests in a loop back mode, the
> TCP streaming performance is about 7% worse when SLUB is enabled on
> 2.6.21-rc7-mm1 kernel (x86_64).  This test have a lot of sk_buff
> allocation/deallocation.

2.6.21-rc7-mm2 contains some performance fixes that may or may not be 
useful to you.
> 
> For Volanomark, the performance is 7% worse for Woodcrest and 12% worse
> for Clovertown.

SLUBs "queueing" is restricted to the number of objects that fit in page 
order slab. SLAB can queue more objects since it has true queues. 
Increasing the page size that SLUB uses may fix the problem but then we 
run into higher page order issues.

Check slabinfo output for the network slabs and see what order is used. 
The number of objects per slab is important for performance.

--
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-02 19:47 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 [this message]
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
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.0705021243480.1543@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=arjan.van.de.ven@intel.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@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