From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Slab allocators: Define common size limitations
Date: Tue, 15 May 2007 23:32:39 -0700 [thread overview]
Message-ID: <20070515233239.335bd4ed.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705152313490.5832@schroedinger.engr.sgi.com>
On Tue, 15 May 2007 23:15:24 -0700 (PDT) Christoph Lameter <clameter@sgi.com> wrote:
> Currently we have a maze of configuration variables that determine
> the maximum slab size. Worst of all it seems to vary between SLAB and SLUB.
>
> So define a common maximum size for kmalloc. For conveniences sake
> we use the maximum size ever supported which is 32 MB. We limit the maximum
> size to a lower limit if MAX_ORDER does not allow such large allocations.
>
> For many architectures this patch will have the effect of adding large
> kmalloc sizes. x86_64 adds 5 new kmalloc sizes. So a small amount
> of memory will be needed for these caches (contemporary SLAB has dynamically
> sizeable node and cpu structure so the waste is less than in the past)
>
> Most architectures will then be able to allocate object with sizes up to
> MAX_ORDER. We have had repeated breakage (in fact whenever we doubled the
> number of supported processors) on IA64 because one or the other struct
> grew beyond what the slab allocators supported. This will avoid future
> issues and f.e. avoid fixes for 2k and 4k cpu support.
>
> CONFIG_LARGE_ALLOCS is no longer necessary so drop it.
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
>
> ---
> arch/blackfin/Kconfig | 8 --------
> arch/frv/Kconfig | 8 --------
> arch/m68knommu/Kconfig | 8 --------
> arch/v850/Kconfig | 8 --------
> include/linux/kmalloc_sizes.h | 20 +++++++++++++++-----
> include/linux/slab.h | 15 +++++++++++++++
> include/linux/slub_def.h | 19 ++-----------------
> mm/slab.c | 19 ++-----------------
> 8 files changed, 34 insertions(+), 71 deletions(-)
rofl. Really we shouldn't put this into 2.6.22, but it turfs out so much
crap that it's hard to justify holding it back.
--
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-05-16 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 6:15 Christoph Lameter
2007-05-16 6:32 ` Andrew Morton [this message]
2007-05-16 6:39 ` David Miller, Andrew Morton
2007-05-16 6:58 ` Geert Uytterhoeven
2007-05-16 7:02 ` David Miller, Geert Uytterhoeven
2007-05-16 17:41 ` Christoph Lameter
2007-05-16 21:42 ` Arnd Bergmann
2007-05-17 8:45 ` Geert Uytterhoeven
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=20070515233239.335bd4ed.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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