1softirqs(8) System Manager's Manual softirqs(8)
2
3
4
6 softirqs - Measure soft IRQ (soft interrupt) event time. Uses Linux
7 eBPF/bcc.
8
10 softirqs [-h] [-T] [-N] [-C] [-d] [-c CPU] [interval] [count]
11
13 This summarizes the time spent servicing soft IRQs (soft interrupts),
14 and can show this time as either totals or histogram distributions. A
15 system-wide summary of this time is shown by the %soft column of mp‐
16 stat(1), and soft IRQ event counts (but not times) are available in
17 /proc/softirqs.
18
19 This tool uses the irq:softirq_enter and irq:softirq_exit kernel trace‐
20 points, which is a stable tracing mechanism. BPF programs can attach to
21 tracepoints from Linux 4.7 only. An older version of this tool is
22 available in tools/old, and uses kprobes instead of tracepoints.
23
24 Since this uses BPF, only the root user can use this tool.
25
27 CONFIG_BPF and bcc.
28
30 -h Print usage message.
31
32 -T Include timestamps on output.
33
34 -N Output in nanoseconds.
35
36 -C Show the number of soft irq events.
37
38 -d Show IRQ time distribution as histograms.
39
40 -c CPU Trace on this CPU only.
41
43 Sum soft IRQ event time until Ctrl-C:
44 # softirqs
45
46 Show the number of soft irq events:
47 # softirqs -C
48
49 Show soft IRQ event time as histograms:
50 # softirqs -d
51
52 Print 1 second summaries, 10 times:
53 # softirqs 1 10
54
55 1 second summaries, printed in nanoseconds, with timestamps:
56 # softirqs -NT 1
57
58 Sum soft IRQ event time on CPU 1 until Ctrl-C:
59 # softirqs -c 1
60
62 SOFTIRQ
63 The kernel function name that performs the soft IRQ action.
64
65 TOTAL_usecs
66 Total time spent in this soft IRQ function in microseconds.
67
68 TOTAL_nsecs
69 Total time spent in this soft IRQ function in nanoseconds.
70
71 usecs Range of microseconds for this bucket.
72
73 nsecs Range of nanoseconds for this bucket.
74
75 count Number of soft IRQs in this time range.
76
77 distribution
78 ASCII representation of the distribution (the count column).
79
81 This traces kernel functions and maintains in-kernel counts, which are
82 asynchronously copied to user-space. While the rate of interrupts be
83 very high (>1M/sec), this is a relatively efficient way to trace these
84 events, and so the overhead is expected to be small for normal work‐
85 loads, but could become noticeable for heavy workloads. Measure in a
86 test environment before use.
87
89 This is from bcc.
90
91 https://github.com/iovisor/bcc
92
93 Also look in the bcc distribution for a companion _examples.txt file
94 containing example usage, output, and commentary for this tool.
95
97 Linux
98
100 Unstable - in development.
101
103 Brendan Gregg, Sasha Goldshtein, Rocky Xing
104
106 hardirqs(8)
107
108
109
110USER COMMANDS 2015-10-20 softirqs(8)