Christoph Lameter <[email protected]> wrote: > > Make kzalloc a macro and use __GFP_ZERO for zeroed slab allocations > I'd question the usefulness of this. It adds more code to a fastpath (kmem_cache_alloc) so as to speed up a slowpath (kzalloc()) which is already slow due to its memset. It makes my kernel a bit fatter too - 150-odd bytes of text for some reason. - 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/
- Follow-Ups:
- Re: Make kzalloc a macro
- From: Christoph Lameter <[email protected]>
- Re: Make kzalloc a macro
- References:
- Re: making kmalloc BUG() might not be a good idea
- From: Nick Piggin <[email protected]>
- Re: making kmalloc BUG() might not be a good idea
- From: Ingo Oeser <[email protected]>
- Re: making kmalloc BUG() might not be a good idea
- From: Nick Piggin <[email protected]>
- Re: making kmalloc BUG() might not be a good idea
- From: "David S. Miller" <[email protected]>
- Re: making kmalloc BUG() might not be a good idea
- From: Nick Piggin <[email protected]>
- Re: making kmalloc BUG() might not be a good idea
- From: Coywolf Qi Hunt <[email protected]>
- Make kzalloc a macro
- From: Christoph Lameter <[email protected]>
- Re: Make kzalloc a macro
- From: Christoph Lameter <[email protected]>
- Re: making kmalloc BUG() might not be a good idea
- Prev by Date: [RFC] Asynchronous IPI and e1000 Multiple Queues
- Next by Date: [PATCH] ioc4_serial: Remove bogus error message
- Previous by thread: Re: Make kzalloc a macro
- Next by thread: Re: Make kzalloc a macro
- Index(es):
