Prev: Simplify and comment on anon_vma re-use for anon_vma_prepare()
Next: nobootmem: use lmb.default_alloc_limit in alloc_bootmem path
From: Benjamin Herrenschmidt on 13 Apr 2010 06:20
On Mon, 2010-04-12 at 22:46 -0700, H. Peter Anvin wrote:
> On 04/12/2010 10:26 PM, Yinghai wrote:
> >
> > current generic lmb_find_area() is allocating from high to low.
> > x86 32bit seems have problem with that.
>
> Presumably because it fills up ZONE_DMA.

I'm working on some LMB cleanups now, among others trying to take into
account what I think are Yinghai requirements. Give me a few days.

For the specific problem above, my idea is to have the low level alloc
function be able to take both low and high limits, so that x86 can
figure out what's best for a given allocation.

Cheers,
Ben.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2
Prev: Simplify and comment on anon_vma re-use for anon_vma_prepare()
Next: nobootmem: use lmb.default_alloc_limit in alloc_bootmem path