All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@ufl.edu>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: cmrivera@ufl.edu, linux-kernel@vger.kernel.org
Subject: Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct
Date: Sun, 10 Aug 2003 21:07:53 -0700	[thread overview]
Message-ID: <1060574873.684.41.camel@localhost> (raw)
In-Reply-To: <34161.4.4.25.4.1060573727.squirrel@www.osdl.org>

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



  reply	other threads:[~2003-08-11  4:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11  3:33 /proc/stat's intr field looks odd, although /proc/interrupts seems correct Chris Rivera
2003-08-11  3:48 ` Randy.Dunlap
2003-08-11  4:07   ` Robert Love [this message]
2003-08-11  4:33     ` Randy.Dunlap
2003-08-11  4:35       ` Robert Love
2003-08-11  4:41         ` Randy.Dunlap
2003-08-11  4:45           ` Robert Love
2003-08-11  5:23             ` Zwane Mwaikambo
2003-08-11  5:55               ` Zwane Mwaikambo
2003-08-11  6:12                 ` Zwane Mwaikambo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1060574873.684.41.camel@localhost \
    --to=rml@ufl.edu \
    --cc=cmrivera@ufl.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.