On Wed, Mar 02, 2005 at 10:20:38AM +0900, Kenji Kaneshige wrote: > Christoph Hellwig wrote: > >> > >>The problem is naming, I think. Those aren't "cache entries", they > >>are statically preallocated entries. How about changing the config > >>option name to: > > > > > >Even for early allocations what speaks against alloc_bootmem? > > > > > > I didn't use alloc_bootmem because I thought alloc_bootmem was > very simple allocator and we should not use it to allocate > arbitrary size (not PAGE_SIZE * n) of memory so frequently. > But I don't know about it very much and my understanding might > be incorrect. > > Can I use alloc_bootmem as well as kmalloc to allocate arbitrary > size of memory?
alloc_bootmem is pretty stupid so, yes you have to be carefull to avoid too much wastage. - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
