On Tue, 3 Jun 2014, Vladimir Davydov wrote: > Still, I really want to evict all empty slabs from cache on memcg > offline for sure. Handling failures there means introducing a worker > that will retry shrinking, but that seems to me as an unnecessary > complication, because there's nothing that can prevent us from shrinking > empty slabs from the cache, even if we merge slab defragmentation, isn't > it? > > May be, it's worth introducing a special function, say kmem_cache_zap(), > that will only evict empty slabs from the cache, plus disable empty > slabs caching? This function would be called only from memcg offline for > dead memcg caches. I am fine with the lower impact version that you came up with later. -- 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>