Should we use IRQBalance in guests?
-
For a host, irqbalance is a very useful tool, but how is it with guests?
I just installed Alpine from XOA HUB and it looks like this:
localhost:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 0: 6 0 0 0 0 0 IO-APIC 2-edge timer 1: 1184 0 0 0 0 0 xen-pirq 1-ioapic-edge i8042 4: 36 0 0 0 0 0 xen-pirq 4-ioapic-edge ttyS0 6: 2 0 0 0 0 0 xen-pirq 6-ioapic-edge floppy 8: 2 0 0 0 0 0 xen-pirq 8-ioapic-edge rtc0 9: 0 0 0 0 0 0 xen-pirq 9-ioapic-level acpi 12: 86 0 0 0 0 0 xen-pirq 12-ioapic-edge i8042 14: 0 0 0 0 0 0 IO-APIC 14-edge ata_piix 15: 0 0 174 0 0 0 IO-APIC 15-edge ata_piix 23: 590 0 0 0 0 0 xen-pirq -ioapic-level uhci_hcd:usb1 48: 68710 0 0 0 0 0 xen-percpu -virq timer0 49: 3765 0 0 0 0 0 xen-percpu -ipi resched0 50: 866 0 0 0 0 0 xen-percpu -ipi callfunc0 51: 0 0 0 0 0 0 xen-percpu -virq debug0 52: 80 0 0 0 0 0 xen-percpu -ipi callfuncsingle0 53: 0 0 0 0 0 0 xen-percpu -ipi spinlock0 54: 0 16908 0 0 0 0 xen-percpu -virq timer1 55: 0 8840 0 0 0 0 xen-percpu -ipi resched1 56: 0 580 0 0 0 0 xen-percpu -ipi callfunc1 57: 0 0 0 0 0 0 xen-percpu -virq debug1 58: 0 30 0 0 0 0 xen-percpu -ipi callfuncsingle1 59: 0 0 0 0 0 0 xen-percpu -ipi spinlock1 60: 0 0 24405 0 0 0 xen-percpu -virq timer2 61: 0 0 12940 0 0 0 xen-percpu -ipi resched2 62: 0 0 997 0 0 0 xen-percpu -ipi callfunc2 63: 0 0 0 0 0 0 xen-percpu -virq debug2 64: 0 0 32 0 0 0 xen-percpu -ipi callfuncsingle2 65: 0 0 0 0 0 0 xen-percpu -ipi spinlock2 66: 0 0 0 6566 0 0 xen-percpu -virq timer3 67: 0 0 0 3265 0 0 xen-percpu -ipi resched3 68: 0 0 0 828 0 0 xen-percpu -ipi callfunc3 69: 0 0 0 0 0 0 xen-percpu -virq debug3 70: 0 0 0 75 0 0 xen-percpu -ipi callfuncsingle3 71: 0 0 0 0 0 0 xen-percpu -ipi spinlock3 72: 0 0 0 0 8255 0 xen-percpu -virq timer4 73: 0 0 0 0 6154 0 xen-percpu -ipi resched4 74: 0 0 0 0 1013 0 xen-percpu -ipi callfunc4 75: 0 0 0 0 0 0 xen-percpu -virq debug4 76: 0 0 0 0 27 0 xen-percpu -ipi callfuncsingle4 77: 0 0 0 0 0 0 xen-percpu -ipi spinlock4 78: 0 0 0 0 0 15302 xen-percpu -virq timer5 79: 0 0 0 0 0 3389 xen-percpu -ipi resched5 80: 0 0 0 0 0 956 xen-percpu -ipi callfunc5 81: 0 0 0 0 0 0 xen-percpu -virq debug5 82: 0 0 0 0 0 79 xen-percpu -ipi callfuncsingle5 83: 0 0 0 0 0 0 xen-percpu -ipi spinlock5 84: 1711 0 0 0 0 0 xen-dyn -event xenbus 86: 2201 0 0 0 0 0 xen-dyn -event blkif 87: 142 0 0 0 0 0 xen-dyn -event vif0-q0-tx 88: 164237 0 0 0 0 0 xen-dyn -event vif0-q0-rx 89: 682 0 0 0 0 0 xen-dyn -event vif0-q1-tx 90: 8037 0 0 0 0 0 xen-dyn -event vif0-q1-rx 91: 13 0 0 0 0 0 xen-dyn -event vif0-q2-tx 92: 7526 0 0 0 0 0 xen-dyn -event vif0-q2-rx 93: 595 0 0 0 0 0 xen-dyn -event vif0-q3-tx 94: 7857 0 0 0 0 0 xen-dyn -event vif0-q3-rx 95: 66 0 0 0 0 0 xen-dyn -event vif0-q4-tx 96: 7436 0 0 0 0 0 xen-dyn -event vif0-q4-rx 97: 5899 0 0 0 0 0 xen-dyn -event vif0-q5-tx 98: 8321 0 0 0 0 0 xen-dyn -event vif0-q5-rx NMI: 1 1 1 1 1 1 Non-maskable interrupts LOC: 0 0 0 0 0 0 Local timer interrupts SPU: 0 0 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 0 0 Performance monitoring interrupts IWI: 0 0 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 APIC ICR read retries RES: 3765 8840 12941 3265 6155 3390 Rescheduling interrupts CAL: 946 610 1029 903 1040 1035 Function call interrupts TLB: 107 62 62 105 61 117 TLB shootdowns HYP: 287606 26217 38255 10685 15380 19683 Hypervisor callback interrupts HRE: 0 0 0 0 0 0 Hyper-V reenlightenment interrupts HVS: 0 0 0 0 0 0 Hyper-V stimer0 interrupts ERR: 0 MIS: 0 PIN: 0 0 0 0 0 0 Posted-interrupt notification event NPI: 0 0 0 0 0 0 Nested posted-interrupt event PIW: 0 0 0 0 0 0 Posted-interrupt wakeup event -
Any thoughts on this topic? I noticed that Alpine from XO HUB didn't use irqbalance by default.
