mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, nickpiggin@yahoo.com.au,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc2: Network commit causes SLUB performance regression with tbench
Date: Wed, 14 Nov 2007 17:03:25 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711141650150.21965@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20071114.154616.46285694.davem@davemloft.net>

On Wed, 14 Nov 2007, David Miller wrote:

> > As a result, we may allocate more than a page of data in the
> > non-TSO case when exactly one page is desired.

Well this is likely the result of the SLUB regression. If you allocate an 
order 1 page then the zone locks need to be taken. SLAB queues the a 
couple of higher order pages and can so serve a couple of requests without 
going into the page allocator whereas SLUB has to go directly to the page 
allocator for allocate and free. I guess that needs fixing in the page 
allocator. Or do I need to add a mechanism to buffer higher order page 
allcoations to SLUB?



  parent reply	other threads:[~2007-11-15  1:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 12:36 2.6.24-rc2 slab vs slob tbench numbers Nick Piggin
2007-11-09 15:15 ` Christoph Lameter
2007-11-09 17:49   ` Christoph Lameter
2007-11-09 23:46     ` 2.6.24-rc2: Network commit causes SLUB performance regression with tbench Christoph Lameter
2007-11-10  1:29       ` Nick Piggin
2007-11-10  3:28         ` Nick Piggin
2007-11-12 19:44         ` Christoph Lameter
2007-11-13 11:41           ` Nick Piggin
2007-11-14  1:58             ` David Miller
2007-11-13 17:36               ` Nick Piggin
2007-11-14  6:12                 ` David Miller
2007-11-13 18:14                   ` Nick Piggin
2007-11-14  6:37                     ` David Miller
2007-11-13 22:27                       ` Nick Piggin
2007-11-13 22:55                         ` Nick Piggin
2007-11-14 11:10                         ` David Miller
2007-11-13 23:39                           ` Nick Piggin
2007-11-14 11:48                           ` Herbert Xu
2007-11-14  0:02                             ` Nick Piggin
2007-11-14 12:10                               ` David Miller
2007-11-14 18:33                                 ` Christoph Lameter
2007-11-14 23:46                             ` David Miller
2007-11-15  0:21                               ` Nick Piggin
2007-11-15  0:27                                 ` David Miller
2007-11-15  1:03                               ` Christoph Lameter [this message]
2007-11-15  1:11                                 ` Herbert Xu
2007-11-15  1:47                                   ` Nick Piggin
2007-11-12 20:13 ` 2.6.24-rc2 slab vs slob tbench numbers Matt Mackall
2007-11-13 11:44   ` Nick Piggin

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.0711141650150.21965@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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

all inboxes | Powered by JetHome®