Lines Matching +full:line +full:- +full:orders
13 to the kernel command line. That will enable full debugging for
18 slabs that have data in them. See "slabinfo -h" for more options when
22 gcc -o slabinfo tools/mm/slabinfo.c
25 be enabled on the command line. F.e. no tracking information will be
30 -------------------------------------------
35 slab_debug=<Debug-Options>
38 slab_debug=<Debug-Options>,<slab name1>,<slab name2>,...
57 caused higher minimum slab orders
58 - Switch all debugging off (useful if the kernel is
74 slab_debug=P,kmalloc-*,dentry
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.
127 ``slabinfo -a`` displays which slabs were merged together.
136 slabinfo -v
141 In that case ``slabinfo -v`` simply tests all reachable objects. Usually
173 page. Setting command line parameter
193 BUG kmalloc-8: Right Redzone overwritten
194 --------------------------------------------------------------------
196 INFO: 0xc90f6d28-0xc90f6d2b. First byte 0x00 instead of 0xcc
228 FIX kmalloc-8: Restoring Redzone 0xc90f6d28-0xc90f6d2b=0xcc
240 -----------------------------------------------
242 INFO: <corruption start>-<corruption_end> <more info>
255 Various types of lines can follow the BUG SLUB line:
264 typically contain poison values. Any non-poison value shows a
334 The ``slabinfo`` tool has a special 'extended' ('-X') mode that includes:
335 - Slabcache Totals
336 - Slabs sorted by size (up to -N <num> slabs, default 1)
337 - Slabs sorted by loss (up to -N <num> slabs, default 1)
341 also available to other slabinfo modes via '-B' option) which makes
342 reporting more precise and accurate. Moreover, in some sense the `-X'
344 output can be plotted using the ``slabinfo-gnuplot.sh`` script. So it
346 to something easier -- visual analysis.
352 while [ 1 ]; do slabinfo -X >> FOO_STATS; sleep 1; done
354 b) pass stats file(-s) to ``slabinfo-gnuplot.sh`` script::
356 slabinfo-gnuplot.sh FOO_STATS [FOO_STATS2 .. FOO_STATSN]
358 The ``slabinfo-gnuplot.sh`` script will pre-processes the collected records
359 and generates 3 png files (and 3 pre-processing cache files) per STATS
361 - Slabcache Totals: FOO_STATS-totals.png
362 - Slabs sorted by size: FOO_STATS-slabs-by-size.png
363 - Slabs sorted by loss: FOO_STATS-slabs-by-loss.png
365 Another use case, when ``slabinfo-gnuplot.sh`` can be useful, is when you
367 modification. To help you out there, ``slabinfo-gnuplot.sh`` script
373 while [ 1 ]; do slabinfo -X >> STATS<X>; sleep 1; done
375 b) Pre-process those STATS files::
377 slabinfo-gnuplot.sh STATS1 STATS2 .. STATSN
379 c) Execute ``slabinfo-gnuplot.sh`` in '-t' mode, passing all of the
380 generated pre-processed \*-totals::
382 slabinfo-gnuplot.sh -t STATS1-totals STATS2-totals .. STATSN-totals
387 can go unnoticed. To deal with that, ``slabinfo-gnuplot.sh`` has two
388 options to 'zoom-in'/'zoom-out':
390 a) ``-s %d,%d`` -- overwrites the default image width and height
391 b) ``-r %d,%d`` -- specifies a range of samples to use (for example,
392 in ``slabinfo -X >> FOO_STATS; sleep 1;`` case, using a ``-r
413 kmalloc objects(total/per-object), minimal/average/maximal jiffies
419 338 pci_alloc_dev+0x2c/0xa0 waste=521872/1544 age=290837/291891/293509 pid=1 cpus=106 nodes=0-1
440 objects. The freeing traces thus come from the previous life-cycle of the
450 1980 <not-available> age=4294912290 pid=0 cpus=0