Lines Matching +full:d +full:- +full:cache +full:- +full:size
20 slabs that have data in them. See "slabinfo -h" for more options when
24 gcc -o slabinfo tools/vm/slabinfo.c
32 -------------------------------------------
37 slub_debug=<Debug-Options>
40 slub_debug=<Debug-Options>,<slab name1>,<slab name2>,...
52 A Toggle failslab filter mark for the cache
55 - Switch all debugging off (useful if the kernel is
62 Trying to find an issue in the dentry cache? Try::
66 to only enable debugging on the dentry cache. You may use an asterisk at the
68 example, here's how you can poison the dentry cache as well as all kmalloc
71 slub_debug=P,kmalloc-*,dentry
74 to the dentry cache with::
105 in order to reduce overhead and increase cache hotness of objects.
106 ``slabinfo -a`` displays which slabs were merged together.
115 slabinfo -v
120 In that case ``slabinfo -v`` simply tests all reachable objects. Usually
151 of a slab cache with large object sizes into one high order
163 BUG kmalloc-8: Redzone overwritten
164 --------------------------------------------------------------------
166 INFO: 0xc90f6d28-0xc90f6d2b. First byte 0x00 instead of 0xcc
198 FIX kmalloc-8: Restoring Redzone 0xc90f6d28-0xc90f6d2b=0xcc
209 BUG <slab cache affected>: <What went wrong>
210 -----------------------------------------------
212 INFO: <corruption start>-<corruption_end> <more info>
234 typically contain poison values. Any non-poison value shows a
263 FIX <slab cache affected>: <corrective action taken>
289 and enabling debugging only for that cache
304 The ``slabinfo`` tool has a special 'extended' ('-X') mode that includes:
305 - Slabcache Totals
306 - Slabs sorted by size (up to -N <num> slabs, default 1)
307 - Slabs sorted by loss (up to -N <num> slabs, default 1)
311 also available to other slabinfo modes via '-B' option) which makes
312 reporting more precise and accurate. Moreover, in some sense the `-X'
314 output can be plotted using the ``slabinfo-gnuplot.sh`` script. So it
316 to something easier -- visual analysis.
322 while [ 1 ]; do slabinfo -X >> FOO_STATS; sleep 1; done
324 b) pass stats file(-s) to ``slabinfo-gnuplot.sh`` script::
326 slabinfo-gnuplot.sh FOO_STATS [FOO_STATS2 .. FOO_STATSN]
328 The ``slabinfo-gnuplot.sh`` script will pre-processes the collected records
329 and generates 3 png files (and 3 pre-processing cache files) per STATS
331 - Slabcache Totals: FOO_STATS-totals.png
332 - Slabs sorted by size: FOO_STATS-slabs-by-size.png
333 - Slabs sorted by loss: FOO_STATS-slabs-by-loss.png
335 Another use case, when ``slabinfo-gnuplot.sh`` can be useful, is when you
337 modification. To help you out there, ``slabinfo-gnuplot.sh`` script
343 while [ 1 ]; do slabinfo -X >> STATS<X>; sleep 1; done
345 b) Pre-process those STATS files::
347 slabinfo-gnuplot.sh STATS1 STATS2 .. STATSN
349 c) Execute ``slabinfo-gnuplot.sh`` in '-t' mode, passing all of the
350 generated pre-processed \*-totals::
352 slabinfo-gnuplot.sh -t STATS1-totals STATS2-totals .. STATSN-totals
357 can go unnoticed. To deal with that, ``slabinfo-gnuplot.sh`` has two
358 options to 'zoom-in'/'zoom-out':
360 a) ``-s %d,%d`` -- overwrites the default image width and heigh
361 b) ``-r %d,%d`` -- specifies a range of samples to use (for example,
362 in ``slabinfo -X >> FOO_STATS; sleep 1;`` case, using a ``-r