Documentation/mm/slub.rst

5 The basic philosophy of SLUB is very different from SLAB. SLAB
7 slab caches. SLUB always includes full debugging but it is off by default.
32 Parameters may be given to ``slub_debug``. If none is specified then full
33 debugging is enabled. Format:
43 blocks of options delimited by ';'. The last of "all slabs" blocks is applied
58 	-		Switch all debugging off (useful if the kernel is
107 If the file contains 1, the option is enabled, 0 means disabled. The debug
117 failslab file is writable, so writing 1 or 0 will enable or disable
118 the option at runtime. Write returns -EINVAL if cache is an alias.
125 If no debug options are specified then SLUB may merge similar slabs together
148 To some degree SLUB's performance is limited by the need to take the
149 list_lock once in a while to deal with partial slabs. That overhead is
170 	longer be checked. This is useful to avoid SLUB trying to
181 Here is a sample of slub debug output::
241    (Object allocation / free information is only available if SLAB_STORE_USER is
254 	The bytes of the object. If the object is inactive then the bytes
259 	The Redzone following the object. The Redzone is used to detect
261 	value. If there is any deviation then it is due to a write after
264 	(Redzone information is only available if SLAB_RED_ZONE is set.
276    of the corruption is may be more likely found by looking at the function that
331 sizes (G/M/K) and reports everything in bytes (this functionality is
349    The ``slabinfo-gnuplot.sh`` script will pre-processes the collected records
350    and generates 3 png files (and 3 pre-processing cache files) per STATS
356 Another use case, when ``slabinfo-gnuplot.sh`` can be useful, is when you
359 can 'merge' the `Slabcache Totals` sections from different
371    generated pre-processed \*-totals::
400     allocated objects. The output is sorted by frequency of each trace.
433     time. The output is sorted by frequency of each trace.