On Wed, 12 Feb 2020, Andrew Morton wrote: > : reading "/proc/slabinfo" can possibly block the slab allocation on > : another CPU for a while, 200ms in extreme cases > > That was bad of us. It would be good to stop doing this. The count is not needed for any operations. Just for the slabinfo output. The value has no operational value for the allocator itself. So why use extra logic to track it in potentially performance critical paths? One could estimate the number of objects from the number of allocated slabs instead?
