Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct
From: Robert Love (rml_at_ufl.edu)
Date: 08/11/03
- Previous message: Randy.Dunlap: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
- In reply to: Randy.Dunlap: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
- Next in thread: Randy.Dunlap: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
- Reply: Randy.Dunlap: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "Randy.Dunlap" <rddunlap@osdl.org> Date: Sun, 10 Aug 2003 21:07:53 -0700
On Sun, 2003-08-10 at 20:48, Randy.Dunlap wrote:
> Yes, for most architectures, it prints interrupts from 0 thru NR_IRQS:
> for (i = 0 ; i < NR_IRQS ; i++)
> len += sprintf(page + len, " %u", kstat_irqs(i));
> and NR_IRQS varies depending on the kernel build options, but (for x86)
> is usually either 16 or 224.
Eww. So I guess on SMP, it is 224.
Might be nice to only print lines that are registered, like
/proc/interrupts. But then you have no way of knowing which field is
which interrupt line. Ugh.
How can we expect anything to parse that line?
Robert Love
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Randy.Dunlap: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
- In reply to: Randy.Dunlap: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
- Next in thread: Randy.Dunlap: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
- Reply: Randy.Dunlap: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
