mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: cl@linux-foundation.org, Andi Kleen <andi@firstfloor.org>,
	Matthew Wilcox <matthew@wil.cx>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	linux-kernel@vger.kernel.org, akmp@linux-foundation.org
Subject: Re: [PATCH] SLUB: revert direct page allocator pass through
Date: Fri, 23 Jan 2009 17:22:31 +0800	[thread overview]
Message-ID: <1232702551.11429.175.camel@ymzhang> (raw)
In-Reply-To: <Pine.LNX.4.64.0901231041210.8574@melkki.cs.Helsinki.FI>

On Fri, 2009-01-23 at 10:43 +0200, Pekka J Enberg wrote:
> From: Pekka Enberg <penberg@cs.helsinki.fi>
> 
> This patch reverts page allocator pass-through logic from the SLUB allocator.
> 
> Commit aadb4bc4a1f9108c1d0fbd121827c936c2ed4217 ("SLUB: direct pass through of
> page size or higher kmalloc requests") added page allocator pass-through to the
> SLUB allocator for large sized allocations. This, however, results in a
> performance regression compared to SLAB in the netperf UDP-U-4k test.
> 
> The regression comes from the kfree(skb->head) call in skb_release_data() that
> is subject to page allocator pass-through as the size passed to __alloc_skb()
> is larger than 4 KB in this test. With this patch, the performance regression
> is almost closed:
> 
>   <insert numbers here>
> 
> Reported-by: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
> Tested-by: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
> Yanmin, do you still have the relevant numbers I could cut and paste to 
> the patch description?
I use 2.6.29-rc2 kernel to run netperf UDP-U-4k CPU_NUM client/server pair loopback testing
on x86-64 machines. Comparing with SLUB, SLAB's result is about 2.3 times of SLUB's.
After applying the reverting patch, the result difference between SLUB and SLAB becomes 1%
which we might consider as fluctuation.

yanmin



      parent reply	other threads:[~2009-01-23  9:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23  8:43 Pekka J Enberg
2009-01-23  8:52 ` Nick Piggin
2009-01-23  9:04   ` Pekka Enberg
2009-01-23 15:03   ` Christoph Lameter
2009-01-23 15:12     ` Nick Piggin
2009-01-23 15:27       ` Christoph Lameter
2009-01-23 15:37         ` Nick Piggin
2009-01-23 15:44           ` Pekka Enberg
2009-01-23 15:54             ` Nick Piggin
2009-01-23 16:07               ` Pekka Enberg
2009-01-23 15:57           ` Christoph Lameter
2009-01-23 16:03             ` Pekka Enberg
2009-01-24  3:11           ` Zhang, Yanmin
2009-01-23 15:16     ` Pekka Enberg
2009-01-23 15:25       ` Christoph Lameter
2009-01-23 15:41         ` Nick Piggin
2009-01-23 15:59           ` Christoph Lameter
2009-01-23 16:17             ` Nick Piggin
2009-01-26 17:17               ` Christoph Lameter
2009-02-03  1:33                 ` Nick Piggin
2009-02-03 17:08                   ` Christoph Lameter
2009-01-23 15:42         ` Pekka Enberg
2009-01-23 20:12     ` Matt Mackall
2009-01-23  9:22 ` Zhang, Yanmin [this message]

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=1232702551.11429.175.camel@ymzhang \
    --to=yanmin_zhang@linux.intel.com \
    --cc=akmp@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=nickpiggin@yahoo.com.au \
    --cc=penberg@cs.helsinki.fi \
    /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®