Lines Matching +full:d +full:- +full:cache +full:- +full:block +full:- +full:size
18 slabs that have data in them. See "slabinfo -h" for more options when
22 gcc -o slabinfo tools/mm/slabinfo.c
30 -------------------------------------------
35 slab_debug=<Debug-Options>
38 slab_debug=<Debug-Options>,<slab name1>,<slab name2>,...
44 to all slabs except those that match one of the "select slabs" block. Options
55 A Enable failslab filter mark for the cache
58 - Switch all debugging off (useful if the kernel is
65 Trying to find an issue in the dentry cache? Try::
69 to only enable debugging on the dentry cache. You may use an asterisk at the
71 example, here's how you can poison the dentry cache as well as all kmalloc
74 slab_debug=P,kmalloc-*,dentry
77 to the dentry cache with::
93 slab_debug=Z,dentry;U,kmalloc-*
98 with "-" as options::
100 slab_debug=FZ;-,zs_handle,zspage
118 the option at runtime. Write returns -EINVAL if cache is an alias.
126 in order to reduce overhead and increase cache hotness of objects.
127 ``slabinfo -a`` displays which slabs were merged together.
136 slabinfo -v
141 In that case ``slabinfo -v`` simply tests all reachable objects. Usually
172 of a slab cache with large object sizes into one high order
184 BUG kmalloc-8: Right Redzone overwritten
185 --------------------------------------------------------------------
187 INFO: 0xc90f6d28-0xc90f6d2b. First byte 0x00 instead of 0xcc
219 FIX kmalloc-8: Restoring Redzone 0xc90f6d28-0xc90f6d2b=0xcc
230 BUG <slab cache affected>: <What went wrong>
231 -----------------------------------------------
233 INFO: <corruption start>-<corruption_end> <more info>
255 typically contain poison values. Any non-poison value shows a
284 FIX <slab cache affected>: <corrective action taken>
310 and enabling debugging only for that cache
325 The ``slabinfo`` tool has a special 'extended' ('-X') mode that includes:
326 - Slabcache Totals
327 - Slabs sorted by size (up to -N <num> slabs, default 1)
328 - Slabs sorted by loss (up to -N <num> slabs, default 1)
332 also available to other slabinfo modes via '-B' option) which makes
333 reporting more precise and accurate. Moreover, in some sense the `-X'
335 output can be plotted using the ``slabinfo-gnuplot.sh`` script. So it
337 to something easier -- visual analysis.
343 while [ 1 ]; do slabinfo -X >> FOO_STATS; sleep 1; done
345 b) pass stats file(-s) to ``slabinfo-gnuplot.sh`` script::
347 slabinfo-gnuplot.sh FOO_STATS [FOO_STATS2 .. FOO_STATSN]
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
352 - Slabcache Totals: FOO_STATS-totals.png
353 - Slabs sorted by size: FOO_STATS-slabs-by-size.png
354 - Slabs sorted by loss: FOO_STATS-slabs-by-loss.png
356 Another use case, when ``slabinfo-gnuplot.sh`` can be useful, is when you
358 modification. To help you out there, ``slabinfo-gnuplot.sh`` script
364 while [ 1 ]; do slabinfo -X >> STATS<X>; sleep 1; done
366 b) Pre-process those STATS files::
368 slabinfo-gnuplot.sh STATS1 STATS2 .. STATSN
370 c) Execute ``slabinfo-gnuplot.sh`` in '-t' mode, passing all of the
371 generated pre-processed \*-totals::
373 slabinfo-gnuplot.sh -t STATS1-totals STATS2-totals .. STATSN-totals
378 can go unnoticed. To deal with that, ``slabinfo-gnuplot.sh`` has two
379 options to 'zoom-in'/'zoom-out':
381 a) ``-s %d,%d`` -- overwrites the default image width and height
382 b) ``-r %d,%d`` -- specifies a range of samples to use (for example,
383 in ``slabinfo -X >> FOO_STATS; sleep 1;`` case, using a ``-r
393 /sys/kernel/debug/slab/<cache>/ (created only for caches with enabled user
404 kmalloc objects(total/per-object), minimal/average/maximal jiffies
410 338 pci_alloc_dev+0x2c/0xa0 waste=521872/1544 age=290837/291891/293509 pid=1 cpus=106 nodes=0-1
431 objects. The freeing traces thus come from the previous life-cycle of the
441 1980 <not-available> age=4294912290 pid=0 cpus=0