1) number of used objects
2) number of allocated objects
3) size of each object
4) number of slabs that are at least partially in use
5) number of slabs that are allocated for the cache
i.e. 5)-4) are the number of freeable slabs in the cache
6) size in pages for a slab
:
7) length of the per-cpu list. Each cpu some objects in a local list it
can use without acquiring a spinlock
8) batch count. If the per-cpu list overflows multiple objects are
freed/allocated in one block.
7 and 8 are only present if your kernel is compiled for SMP, root can
tune them with
#echo "<slab name> <length> <batchcount>" > /proc/slabinfo
It seems that the dentry cache is severely fragmented, nearly 20 MB (or
30%) are
unfreeable due to fragmentation.
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/