On Thu, 10 Dec 2015, Vladimir Davydov wrote: > IMHO kmem_cache_alloc_bulk/kfree_bulk looks awkward, especially taking > into account the fact that we pair kmem_cache_alloc/kmem_cache_free and > kmalloc/kfree, but never kmem_cache_alloc/kfree. > > So I'd vote for kmem_cache_free_bulk taking a kmem_cache as an argument, > but I'm not a potential user of this API, so please don't count my vote > :-) One way to have it less awkward is to keep naming it kmem_cache_free_bulk but omit the kmem_cache parameter like what I did initially. -- 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>