Re: CK5 [03/18] create common functions for boot slab creation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 1 Nov 2012, Christoph Lameter wrote:

> Use a special function to create kmalloc caches and use that function in
> SLAB and SLUB.
> 
> V1->V2:
> 	Do check for slasb state in slub's __kmem_cache_create to avoid
> 	unlocking a lock that was not taken
> V2->V3:
> 	Remove slab_state check from sysfs_slab_add(). [Joonsoo]
> 
> V3->V4:
> 	- Use %zd instead of %td for size info.
> 	- Do not add slab caches to the list of slab caches during early
> 	  boot.
> 
> Acked-by: Joonsoo Kim <js1304@xxxxxxxxx>
> Reviewed-by: Glauber Costa <glommer@xxxxxxxxxxxxx>
> Signed-off-by: Christoph Lameter <cl@xxxxxxxxx>

Acked-by: David Rientjes <rientjes@xxxxxxxxxx>

Eek, the calls to __kmem_cache_create() in the boot path as it sits in 
slab/next right now are ignoring SLAB_PANIC.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]