Lines Matching +full:no +full:- +full:high +full:- +full:z
17 slabs that have data in them. See "slabinfo -h" for more options when
21 gcc -o slabinfo tools/mm/slabinfo.c
24 be enabled on the command line. F.e. no tracking information will be
29 -------------------------------------------
34 slab_debug=<Debug-Options>
37 slab_debug=<Debug-Options>,<slab name1>,<slab name2>,...
38 Enable options only for select slabs (no spaces
50 Z Red zoning
57 - Switch all debugging off (useful if the kernel is
73 slab_debug=P,kmalloc-*,dentry
83 in low memory situations or if there's high fragmentation of memory. To
92 slab_debug=Z,dentry;U,kmalloc-*
97 with "-" as options::
99 slab_debug=FZ;-,zs_handle,zspage
110 Z red_zone
117 the option at runtime. Write returns -EINVAL if cache is an alias.
124 If no debug options are specified then SLUB may merge similar slabs together
126 ``slabinfo -a`` displays which slabs were merged together.
135 slabinfo -v
140 In that case ``slabinfo -v`` simply tests all reachable objects. Usually
168 specified the order at which ``slab_min_objects`` should no
171 of a slab cache with large object sizes into one high order
192 BUG kmalloc-8: Right Redzone overwritten
193 --------------------------------------------------------------------
195 INFO: 0xc90f6d28-0xc90f6d2b. First byte 0x00 instead of 0xcc
227 FIX kmalloc-8: Restoring Redzone 0xc90f6d28-0xc90f6d2b=0xcc
239 -----------------------------------------------
241 INFO: <corruption start>-<corruption_end> <more info>
263 typically contain poison values. Any non-poison value shows a
313 continual stream of error messages to the syslog but no additional memory
316 No guarantees. The kernel component still needs to be fixed. Performance
333 The ``slabinfo`` tool has a special 'extended' ('-X') mode that includes:
334 - Slabcache Totals
335 - Slabs sorted by size (up to -N <num> slabs, default 1)
336 - Slabs sorted by loss (up to -N <num> slabs, default 1)
340 also available to other slabinfo modes via '-B' option) which makes
341 reporting more precise and accurate. Moreover, in some sense the `-X'
343 output can be plotted using the ``slabinfo-gnuplot.sh`` script. So it
345 to something easier -- visual analysis.
351 while [ 1 ]; do slabinfo -X >> FOO_STATS; sleep 1; done
353 b) pass stats file(-s) to ``slabinfo-gnuplot.sh`` script::
355 slabinfo-gnuplot.sh FOO_STATS [FOO_STATS2 .. FOO_STATSN]
357 The ``slabinfo-gnuplot.sh`` script will pre-processes the collected records
358 and generates 3 png files (and 3 pre-processing cache files) per STATS
360 - Slabcache Totals: FOO_STATS-totals.png
361 - Slabs sorted by size: FOO_STATS-slabs-by-size.png
362 - Slabs sorted by loss: FOO_STATS-slabs-by-loss.png
364 Another use case, when ``slabinfo-gnuplot.sh`` can be useful, is when you
366 modification. To help you out there, ``slabinfo-gnuplot.sh`` script
372 while [ 1 ]; do slabinfo -X >> STATS<X>; sleep 1; done
374 b) Pre-process those STATS files::
376 slabinfo-gnuplot.sh STATS1 STATS2 .. STATSN
378 c) Execute ``slabinfo-gnuplot.sh`` in '-t' mode, passing all of the
379 generated pre-processed \*-totals::
381 slabinfo-gnuplot.sh -t STATS1-totals STATS2-totals .. STATSN-totals
386 can go unnoticed. To deal with that, ``slabinfo-gnuplot.sh`` has two
387 options to 'zoom-in'/'zoom-out':
389 a) ``-s %d,%d`` -- overwrites the default image width and height
390 b) ``-r %d,%d`` -- specifies a range of samples to use (for example,
391 in ``slabinfo -X >> FOO_STATS; sleep 1;`` case, using a ``-r
412 kmalloc objects(total/per-object), minimal/average/maximal jiffies
418 338 pci_alloc_dev+0x2c/0xa0 waste=521872/1544 age=290837/291891/293509 pid=1 cpus=106 nodes=0-1
439 objects. The freeing traces thus come from the previous life-cycle of the
449 1980 <not-available> age=4294912290 pid=0 cpus=0