tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: RFC: IRQ affinity (aka interrupt routing)
On Thu, Aug 21, 2014 at 10:50:53AM +0900, Kengo NAKAHARA wrote:
> Hi,
>
> (2014/08/20 18:46), Martin Husemann wrote:
> >On Wed, Aug 20, 2014 at 06:38:35PM +0900, Kengo NAKAHARA wrote:
> >>I use IRQ number to idetify interrupts. The number is shown "IRQ" column.
> >>Actually, the value equals to struct intrsource.is_pin.
> >
> >Isn't a string (like in vmstat -i output) better?
>
> I think IRQ number is better. Because it is short :)
> Therefore, vmstat -iv output is differ little from IRQ number. For example,
> here is the output of my machine
> ====================
> interrupt total rate
> TLB shootdown 732 0
> cpu0 timer 151842 100
> ioapic0 pin 9 0 0
> ioapic0 pin 20 0 0
> ioapic0 pin 21 0 0
> ioapic0 pin 22 0 0
> ioapic0 pin 23 1816 1
> ioapic0 pin 19 1807 1
> ioapic0 pin 18 0 0
> ioapic0 pin 4 0 0
> ioapic0 pin 3 0 0
> Total 156197 103
> ====================
> Currently, intrctl list does not show "TLB shootdown" and "cpu0 timer".
> Furthermore, "ioapic0 pin 9" of vmstat -iv equals to "9" of intrctl list,
> "ioapic0 pin 20" of vmstat -iv equals to "20" of intrctl list, and so on.
On a x86 server here:
interrupt total rate
TLB shootdown 788900019 295
cpu0 timer 265870470 99
ioapic0 pin 9 0 0
ioapic0 pin 16 1491906220 557
ioapic1 pin 14 153885893 57
ioapic0 pin 17 2731 0
ioapic3 pin 0 13 0
ioapic3 pin 1 14 0
ioapic0 pin 21 789 0
ioapic0 pin 20 15285596 5
ioapic0 pin 14 1 0
ioapic0 pin 4 0 0
ioapic0 pin 3 353 0
Total 2715852099 1015
Notice we have both 'ioapic0 pin 14' and 'ioapic1 pin 14',
what number would be used for intrctl in this case ?
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index