On Tue, Jun 03, 2014 at 09:48:51AM -0500, Christoph Lameter wrote: > 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.
Oh, I missed a couple of your previous e-mails, because our mail server marked them (along with a hundred or so another messages :-) ) as junk for some reason. Going to turn off the filter completely. Sorry for being inconsistent and thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
