summaryrefslogtreecommitdiffstats
path: root/web
diff options
context:
space:
mode:
authorIlya Mashchenko <ilya@netdata.cloud>2021-09-28 10:16:27 +0300
committerGitHub <noreply@github.com>2021-09-28 10:16:27 +0300
commit767203fe3ee4011a32b11925640446b3ada8b606 (patch)
tree5d3a963b60429b0390bdba58c83894fbc4e5e734 /web
parent652bb9d0ed2995726bce9c6cb952f0bbdee739b9 (diff)
add proc_softirqs charts info (#11577)
Diffstat (limited to 'web')
-rw-r--r--web/gui/dashboard_info.js28
1 files changed, 27 insertions, 1 deletions
diff --git a/web/gui/dashboard_info.js b/web/gui/dashboard_info.js
index 77eaf3cfcb..b95e2ac8fc 100644
--- a/web/gui/dashboard_info.js
+++ b/web/gui/dashboard_info.js
@@ -930,6 +930,21 @@ netdataDashboard.submenu = {
'<b>software</b> (generated by programs when they want to request a system call to be performed by the operating system), and '+
'<b>traps</b> (generated by the CPU itself to indicate that some error or condition occurred for which assistance from the operating system is needed).'
},
+
+ 'system.softirqs': {
+ info: 'Software interrupts (or "softirqs") are one of the oldest deferred-execution mechanisms in the kernel. '+
+ 'Several tasks among those executed by the kernel are not critical: '+
+ 'they can be deferred for a long period of time, if necessary. '+
+ 'The deferrable tasks can execute with all interrupts enabled '+
+ '(softirqs are patterned after hardware interrupts). '+
+ 'Taking them out of the interrupt handler helps keep kernel response time small.'
+ },
+
+ 'cpu.softirqs': {
+ info: 'Total number of software interrupts per CPU. '+
+ 'To see the total number for the system check the <a href="#menu_system_submenu_softirqs">softirqs</a> section.'
+ },
+
'cpu.interrupts': {
info: 'Total number of interrupts per CPU. '+
'To see the total number for the system check the <a href="#menu_system_submenu_interrupts">interrupts</a> section. '+
@@ -1047,7 +1062,18 @@ netdataDashboard.context = {
},
'system.softirqs': {
- info: 'CPU softirqs in detail. At the <a href="#menu_cpu">CPUs</a> section, softirqs are analyzed per CPU core.'
+ info: '<p>Total number of software interrupts in the system. '+
+ 'At the <a href="#menu_cpu">CPUs</a> section, softirqs are analyzed <a href="#menu_cpu_submenu_softirqs">per CPU core</a>.</p>'+
+ '<p><b>HI</b> - high priority tasklets. '+
+ '<b>TIMER</b> - tasklets related to timer interrupts. '+
+ '<b>NET_TX</b>, <b>NET_RX</b> - used for network transmit and receive processing. '+
+ '<b>BLOCK</b> - handles block I/O completion events. '+
+ '<b>IRQ_POLL</b> - used by the IO subsystem to increase performance (a NAPI like approach for block devices). '+
+ '<b>TASKLET</b> - handles regular tasklets. '+
+ '<b>SCHED</b> - used by the scheduler to perform load-balancing and other scheduling tasks. '+
+ '<b>HRTIMER</b> - used for high-resolution timers. '+
+ '<b>RCU</b> - performs read-copy-update (RCU) processing.</p>'
+
},
'system.softirq_latency': {