Message-ID: <34253.4.4.25.4.1060576385.squirrel@www.osdl.org>
Date: Sun, 10 Aug 2003 21:33:05 -0700 (PDT)
Subject: Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <rml@ufl.edu>
In-Reply-To: <1060574873.684.41.camel@localhost>
References: <1060572792.1113.10.camel@boobies.awol.org>
        <34161.4.4.25.4.1060573727.squirrel@www.osdl.org>
        <1060574873.684.41.camel@localhost>
Importance: Normal
Cc: <cmrivera@ufl.edu>, <linux-kernel@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 936
Lines: 30

> 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.

Yes.

> 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?

Ugh-ly?  We can move it to sysfs and then change the file format
to intnum:count pairs (e.g.).

~Randy


-
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/