itop problem

[GreyGeek]

I installed itop from the repository, hoping to see how my interrupts were working, and which were the hogs. On my KDE Neon User Edition it didn't work. It displays the column titles and hangs. I got the latest perl script from kargig at GitHub and took a look at the script. The script opens /proc/interrupts and parses it.

I opened /proc/interrupts with kate (not bothering to use kdesuo) and all the information I wanted was displayed in a nice grid format will full names and descriptions, not annoying abbreviations. When I hit the F5 key the information updated (reloaded). So, I didn't need itop. A little menu edit magic and I have an "itop" in my menu that opens /proc/interrupts with kate.

[Simon]

Whoot! +1 GreyGeek

Now one question... what does this mean?

           CPU0       CPU1       
 0:         46          0   IO-APIC-edge      timer
 1:          1          1   IO-APIC-edge      i8042
 7:          0          0   IO-APIC-edge      parport0
 8:          1          0   IO-APIC-edge      rtc0
 9:          0          0   IO-APIC-fasteoi   acpi
12:          2          2   IO-APIC-edge      i8042
14:     103867     201157   IO-APIC-edge      ata_piix
15:          0          0   IO-APIC-edge      ata_piix
16:    3104476    3246471   IO-APIC  16-fasteoi   uhci_hcd:usb5, snd_hda_intel
18:          0          0   IO-APIC  18-fasteoi   uhci_hcd:usb4
19:    3031722    3125379   IO-APIC  19-fasteoi   ata_piix, uhci_hcd:usb3
23:    1886912    1992973   IO-APIC  23-fasteoi   ehci_hcd:usb1, uhci_hcd:usb2
27:   15084284         48   PCI-MSI-edge      eth0
28:   12738900   13263612   PCI-MSI-edge      radeon
30:        317        305   PCI-MSI-edge      snd_hda_intel
NMI:      89161      93958   Non-maskable interrupts
LOC:   77378245   76918656   Local timer interrupts
SPU:          0          0   Spurious interrupts
PMI:      89161      93958   Performance monitoring interrupts
IWI:          2          0   IRQ work interrupts
RTR:          0          0   APIC ICR read retries
RES:  167792387  167977549   Rescheduling interrupts
CAL:      68311       6599   Function call interrupts
TLB:    1485064    1551197   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:       1518       1518   Machine check polls
HYP:          0          0   Hypervisor callback interrupts
ERR:          0
MIS:          0

[jlittle]

Now one question... what does this mean?

From man proc:

/proc/interrupts
This is used to record the number of interrupts per CPU per IO device. Since Linux 2.6.24, for the i386 and x86_64 architectures, at least, this also includes interrupts internal to the system (that is, not associated with a device as such), such as NMI (nonmaskable interrupt), LOC (local timer interrupt), and for SMP systems, TLB (TLB flush interrupt), RES (rescheduling interrupt), CAL (remote function call interrupt), and possibly others. Very easy to read formatting, done in ASCII.

If you're not familiar with PC interrupts, maybe check out the wikipedia article.