1slabratetop(8) System Manager's Manual slabratetop(8)
2
3
4
6 slabratetop - Kernel SLAB/SLUB memory cache allocation rate top. Uses
7 Linux BPF/bcc.
8
10 slabratetop [-h] [-C] [-r MAXROWS] [interval] [count]
11
13 This is top for the the rate of kernel SLAB/SLUB memory allocations.
14 It works by tracing kmem_cache_alloc() calls, a commonly used interface
15 for kernel memory allocation (SLAB or SLUB). It summarizes the rate and
16 total bytes allocated of these calls per interval: the activity. Com‐
17 pare this to slabtop(1), which shows the current static volume of the
18 caches.
19
20 This tool uses kernel dynamic tracing of the kmem_cache_alloc() func‐
21 tion.
22
23 Since this uses BPF, only the root user can use this tool.
24
26 CONFIG_BPF and bcc.
27
29 -C Don't clear the screen.
30
31 -r MAXROWS
32 Maximum number of rows to print. Default is 20.
33
34 interval
35 Interval between updates, seconds.
36
37 count Number of interval summaries.
38
40 Summarize active kernel SLAB/SLUB calls (kmem_cache_alloc()), showing
41 the top 20 caches every second:
42 # slabratetop
43
44 Don't clear the screen, and top 8 rows only:
45 # slabratetop -Cr 8
46
47 5 second summaries, 10 times only:
48 # slabratetop 5 10
49
51 loadavg:
52 The contents of /proc/loadavg
53
54 CACHE Kernel cache name.
55
56 ALLOCS Allocations (number of calls).
57
58 BYTES Total bytes allocated.
59
61 If kmem_cache_alloc() is called at a high rate (eg, >100k/second) the
62 overhead of this tool might begin to be measurable. The rate can be
63 seen in the ALLOCS column of the output.
64
66 This is from bcc.
67
68 https://github.com/iovisor/bcc
69
70 Also look in the bcc distribution for a companion _examples.txt file
71 containing example usage, output, and commentary for this tool.
72
74 Linux
75
77 Unstable - in development.
78
80 Brendan Gregg
81
83 slabtop(1)
84
85
86
87USER COMMANDS 2016-10-17 slabratetop(8)