On Mon, 2006-05-08 at 22:49 -0700, Andrew Morton wrote:
> Mike Kravetz <[email protected]> wrote:
> >
> > There are a few places that check the system_state variable to
> > determine if they should use the bootmem or kmalloc allocator.
> > However, this is not accurate as system_state transitions from
> > SYSTEM_BOOTING to SYSTEM_RUNNING well after the bootmem allocator
> > is no longer usable. Introduce the SYSTEM_BOOTING_KMALLOC_AVAIL
> > state which indicates the kmalloc allocator is available for use.
>
> Let's not do this - system_state is getting out of control.
>
> How about some private boolean in slab.c, and some special allocation
> function like
>
> void __init *alloc_memory_early(size_t size, gfp_t gfp_flags)
> {
> if (slab_is_available)
> return kmalloc(size, gfp_flags);
> return alloc_bootmem(size);
> }
One issue with that approach is that you can't use it for larger
allocations (which we have a lot of at boot-time). Would it be OK to
fall back to the raw page allocator for things where kmalloc() fails?
Oh, and do we want to make it explicitly NUMA aware?
-- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
