On Mon, Jun 02, 2014 at 10:16:03AM -0500, Christoph Lameter wrote: > On Sat, 31 May 2014, Vladimir Davydov wrote: > > > > Well slub returns an error code if it fails > > > > ... to sort slabs by the nubmer of objects in use, which is not even > > implied by the function declaration. Why can *shrinking*, which is what > > kmem_cache_shrink must do at first place, ever fail? > > Because there is a memory allocation failure. Or there may be other > processes going on that prevent shrinking. F.e. We may want to merge a > patchset that does defragmentation of slabs at some point. Fair enough. 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. Thanks. -- 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>