From: Christoph Lameter <clameter@sgi.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Slab allocators: Define common size limitations
Date: Wed, 16 May 2007 10:41:49 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705161039260.9142@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0705160855470.24080@pademelon.sonytel.be>
On Wed, 16 May 2007, Geert Uytterhoeven wrote:
> On Tue, 15 May 2007, Christoph Lameter wrote:
> > 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.
>
> What are the changes a large allocation will actually succeed?
> Is there an alignment rule for large allocations?
>
> E.g. for one of the PS3 drivers I need a physically contiguous 256 KiB-aligned
> block of 256 KiB. Currently I'm using __alloc_bootmem() for that, but maybe
> kmalloc() becomes a suitable alternative now?
The chance of succeeding drops with the time that the system has been
running. Typically these large allocs are used when the system is brought
up. Maybe we will be able to successfully allocate these even after
memory has gotten significant use when Mel's antifrag/defrag work has
progressed more.
next prev parent reply other threads:[~2007-05-16 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0705152313490.5832@schroedinger.engr.sgi.com>
2007-05-16 6:58 ` Slab allocators: Define common size limitations Geert Uytterhoeven
2007-05-16 7:02 ` David Miller
2007-05-16 17:41 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0705161039260.9142@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).