On Tue, 16 Jun 2015, Joonsoo Kim wrote: > So, in your test, most of objects may come from one or two slabs and your > algorithm is well optimized for this case. But, is this workload normal case? It is normal if the objects were bulk allocated because SLUB ensures that all objects are first allocated from one page before moving to another. > If most of objects comes from many different slabs, bulk free API does > enabling/disabling interrupt very much so I guess it work worse than > just calling __kmem_cache_free_bulk(). Could you test this case? In case of SLAB this would be an issue since the queueing mechanism destroys spatial locality. This is much less an issue for SLUB. -- 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>