On Wed, 16 May 2007, Arnd Bergmann wrote:
> On Wednesday 16 May 2007, Geert Uytterhoeven wrote:
> > 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
> > K
On Wednesday 16 May 2007, Geert Uytterhoeven wrote:
> 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 __allo
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 allo
From: Geert Uytterhoeven <[EMAIL PROTECTED]>
Date: Wed, 16 May 2007 08:58:39 +0200 (CEST)
> 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?
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
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Tue, 15 May 2007 23:32:39 -0700
> 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.
If fixes sparc64 with SLAB for one thing. I was going to put
LARGE_ALLOCS back into sparc64/K
On Tue, 15 May 2007 23:15:24 -0700 (PDT) Christoph Lameter <[EMAIL PROTECTED]>
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 convenienc
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 lo
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 lo
9 matches
Mail list logo
