From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, Marcelo Tosatti <marcelo@kvack.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mpm@selenic.com, Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [SLUB 2/3] Large kmalloc pass through. Removal of large general slabs
Date: Wed, 07 Mar 2007 10:01:17 +0100 [thread overview]
Message-ID: <1173258077.6374.120.camel@twins> (raw)
In-Reply-To: <20070307023513.19658.81228.sendpatchset@schroedinger.engr.sgi.com>
On Tue, 2007-03-06 at 18:35 -0800, Christoph Lameter wrote:
> Unlimited kmalloc size and removal of general caches >=4.
>
> We can directly use the page allocator for all allocations 4K and larger. This
> means that no general slabs are necessary and the size of the allocation passed
> to kmalloc() can be arbitrarily large. Remove the useless general caches over 4k.
>
> Index: linux-2.6.21-rc2-mm1/include/linux/slub_def.h
> ===================================================================
> --- linux-2.6.21-rc2-mm1.orig/include/linux/slub_def.h 2007-03-06 17:56:14.000000000 -0800
> +++ linux-2.6.21-rc2-mm1/include/linux/slub_def.h 2007-03-06 17:57:11.000000000 -0800
> @@ -55,7 +55,7 @@ struct kmem_cache {
> */
> #define KMALLOC_SHIFT_LOW 3
>
> -#define KMALLOC_SHIFT_HIGH 18
> +#define KMALLOC_SHIFT_HIGH 11
>
> #if L1_CACHE_BYTES <= 64
> #define KMALLOC_EXTRAS 2
> @@ -93,13 +93,6 @@ static inline int kmalloc_index(int size
> if (size <= 512) return 9;
> if (size <= 1024) return 10;
> if (size <= 2048) return 11;
> - if (size <= 4096) return 12;
> - if (size <= 8 * 1024) return 13;
> - if (size <= 16 * 1024) return 14;
> - if (size <= 32 * 1024) return 15;
> - if (size <= 64 * 1024) return 16;
> - if (size <= 128 * 1024) return 17;
> - if (size <= 256 * 1024) return 18;
> return -1;
> }
Perhaps so something with PAGE_SIZE here, as you know there are
platforms/configs where PAGE_SIZE != 4k :-)
--
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>
next prev parent reply other threads:[~2007-03-07 9:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 2:35 [SLUB 0/3] SLUB: The unqueued slab allocator V4 Christoph Lameter
2007-03-07 2:35 ` [SLUB 1/3] SLUB core Christoph Lameter
2007-03-07 2:35 ` [SLUB 2/3] Large kmalloc pass through. Removal of large general slabs Christoph Lameter
2007-03-07 2:40 ` Matt Mackall
2007-03-07 3:22 ` Christoph Lameter
2007-03-07 9:01 ` Peter Zijlstra [this message]
2007-03-07 15:34 ` Christoph Lameter
2007-03-07 18:03 ` Matt Mackall
2007-03-07 18:23 ` Christoph Lameter
2007-03-07 2:35 ` [SLUB 3/3] Guarantee minimum number of objects in a slab Christoph Lameter
2007-03-08 10:54 ` [SLUB 0/3] SLUB: The unqueued slab allocator V4 Mel Gorman
2007-03-08 16:48 ` Christoph Lameter
2007-03-08 17:40 ` Mel Gorman
2007-03-08 18:16 ` Christoph Lameter
2007-03-09 13:55 ` Mel Gorman
2007-03-08 21:54 ` Christoph Lameter
2007-03-09 14:00 ` Mel Gorman
2007-03-09 16:40 ` Christoph Lameter
2007-03-09 15:06 ` Mel Gorman
2007-03-09 17:21 ` Christoph Lameter
2007-03-08 17:46 ` 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=1173258077.6374.120.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=marcelo@kvack.org \
--cc=mpm@selenic.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