On Tue, 13 Dec 2005, Eric Dumazet wrote: > If this variable is not frequently used, why then define its own cache ? > > Ie why not use kmalloc() and let kernel use a general cache ? I was also wondering why Paul switched to use the slab allocator. One reason may have been to simplify rcu? - 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/
- References:
- [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Eric Dumazet <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Eric Dumazet <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Christoph Lameter <[email protected]>
- Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- From: Eric Dumazet <[email protected]>
- [PATCH] Cpuset: rcu optimization of page alloc hook
- Prev by Date: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
- Next by Date: Re: RFC: ACPI/scsi/libata integration and hotswap
- Previous by thread: Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- Next by thread: Re: [PATCH] Cpuset: rcu optimization of page alloc hook
- Index(es):
 |