> with dyntick kernel (2.6.21), vmstat sometimes report > 0 interrupt. This is because with dyntick, timer interrupt > are not always interupt 0 (pit) but it can be also apic > (counted as local interrypt). > > So vmstat should take care of local interrupt (and may be mmi) > in its report.
If vmstat were reporting interrupt 0 (pic), there would be a huge pile of bug reports from non-x86 users. There would even be a huge pile of bug reports from x86 users, because "interrupt" includes things like disk and network interrupts. The first number on the "intr" line in /proc/stat is the total sum. Interrupt 0 comes next, being from any source (PIC or not) that the CPU will interpret as interrupt 0. You believe that the APIC local interrupt counts as an interrupt. I tend to think that you are correct, but the kernel code doesn't count these. See the kernel's show_stat function, "sum" variable, in the fs/proc/proc_misc.c file. That's what vmstat reports. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
