linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: "Chen, Tim C" <tim.c.chen@intel.com>
Cc: Tim Chen <tim.c.chen@linux.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: Thu, 3 May 2007 17:44:19 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705031740470.15240@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <9D2C22909C6E774EBFB8B5583AE5291C02786032@fmsmsx414.amr.corp.intel.com>

On Thu, 3 May 2007, Chen, Tim C wrote:

> We are still seeing a 5% regression on TCP streaming with
> slub_min_objects set at 16 and a 10% regression for Volanomark, after
> increasing slub_min_objects to 16 and setting slub_max_order=4 and using
> the 2.6.21-rc7-mm2 kernel.  The performance between slub_min_objects=8
> and 16 are similar.

Ok. We then need to look at partial list management. It could be that the 
sequence of partials is reversed. The problem is that I do not really 
have time to concentrate on performance right now. Stability comes 
first. We will likely end up putting some probes in there to find out 
where the overhead comes from.

> > Check slabinfo output for the network slabs and see what order is
> > used. The number of objects per slab is important for performance.
> 
> The order used is 0 for the buffer_head, which is the most used object.
> 
> I think they are 104 bytes per object.

Hmmm.... Then it was not affected by slab_max_order? Try 
slab_min_order=1 or 2 to increase that?

--
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-04  0:44 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 [this message]
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.0705031740470.15240@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