Re: [PATCH] Early kmalloc/kfree

2005-07-11 Thread Alex Williamson
On Sat, 2005-07-09 at 18:06 -0700, Christoph Lameter wrote: > On Fri, 9 Jul 2005, Andi Kleen wrote: > > > I think that is a really really bad idea. slab is already complex enough > > and adding scary hacks like this will probably make it collapse > > under its own weight at some point. > > Seco

Re: [PATCH] Early kmalloc/kfree

2005-07-09 Thread Christoph Lameter
On Fri, 9 Jul 2005, Andi Kleen wrote: > I think that is a really really bad idea. slab is already complex enough > and adding scary hacks like this will probably make it collapse > under its own weight at some point. Seconded. Maybe we can solve this by bringing the system up in a limited con

Re: [PATCH] Early kmalloc/kfree

2005-07-08 Thread Andi Kleen
Bob Picco <[EMAIL PROTECTED]> writes: > We have a requirement on IA64 to run the ACPI interpreter in the setup_arch > function before paging_init examines the maximum DMA physical address which > is limited by the IOMMU. One obstacle is the use of kmalloc/kfree by > ACPI. Using the bootmem alloc

[PATCH] Early kmalloc/kfree

2005-07-08 Thread Bob Picco
We have a requirement on IA64 to run the ACPI interpreter in the setup_arch function before paging_init examines the maximum DMA physical address which is limited by the IOMMU. One obstacle is the use of kmalloc/kfree by ACPI. Using the bootmem allocator is unacceptable because > 20Mb of memory i