From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
yanmin_zhang@linux.intel.com, Andi Kleen <andi@firstfloor.org>,
Matthew Wilcox <matthew@wil.cx>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] SLUB: revert direct page allocator pass through
Date: Fri, 23 Jan 2009 18:03:29 +0200 [thread overview]
Message-ID: <1232726609.6094.106.camel@penberg-laptop> (raw)
In-Reply-To: <alpine.DEB.1.10.0901231055520.32253@qirst.com>
On Sat, 24 Jan 2009, Nick Piggin wrote:
> > However, I don't know if netperf udp 4K over loopback is totally
> > realistic. Maybe real network drivers have different allocation patterns.
> > If I were you I wouldn't be too hasty to make big changes based on that
> > alone, if it could introduce regression in somewhere more important.
On Fri, 2009-01-23 at 10:57 -0500, Christoph Lameter wrote:
> AFAICT it just wastes memory. My idea of a slab allocator is that it is
> used for small (less than page sized) allocations. The page allocator
> should be able to handle page sized allocations in an effective manner.
FWIW, based on my results, it's actually the big objects that are so
badly fitting which causes much of the wasted memory. So I'd prefer to
get rid of the page allocator completely for kmalloc() and just use a
best fit allocator for everything. Something like my binalloc. ;-)
Pekka
next prev parent reply other threads:[~2009-01-23 16:03 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 [this message]
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
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=1232726609.6094.106.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=akpm@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=yanmin_zhang@linux.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
all inboxes | Powered by JetHome®