From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <cmrivera@ufl.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct
Date: Sun, 10 Aug 2003 20:48:47 -0700 (PDT) [thread overview]
Message-ID: <34161.4.4.25.4.1060573727.squirrel@www.osdl.org> (raw)
In-Reply-To: <1060572792.1113.10.camel@boobies.awol.org>
> Hi,
>
> I am running 2.6.0-test2-mm4 on an SMP machine with dual Athlon MP 2000+s.
>
> /proc/stat displays:
>
> cpu 13261 0 2603 887671 4399
> cpu0 6936 0 1571 443183 2285
> cpu1 6325 0 1031 444488 2113
> intr 5021986 4539589 5476 0 0 0 0 0 0 0 0 0 0 73888 0 16345 11 379144 0 7533
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> ctxt 1677244
> btime 1060567182
> processes 1286
> procs_running 1
> procs_blocked 0
>
> /proc/interrupts:
>
> CPU0 CPU1
> 0: 26530 4875571 IO-APIC-edge timer
> 1: 6035 0 IO-APIC-edge i8042
> 2: 0 0 XT-PIC cascade
> 12: 77657 3869 IO-APIC-edge i8042
> 14: 16560 1 IO-APIC-edge ide0
> 15: 11 0 IO-APIC-edge ide1
> 16: 409959 1 IO-APIC-level radeon@PCI:1:5:0
> 17: 0 0 IO-APIC-level EMU10K1
> 18: 7942 0 IO-APIC-level eth0
> NMI: 0 0
> LOC: 4902124 4902123
> ERR: 0
> MIS: 0
>
> I am not sure why the intr line contains all those zeros. Is this normal
> behavior?
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.
~Randy
next prev parent reply other threads:[~2003-08-11 3:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 3:33 Chris Rivera
2003-08-11 3:48 ` Randy.Dunlap [this message]
2003-08-11 4:07 ` Robert Love
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=34161.4.4.25.4.1060573727.squirrel@www.osdl.org \
--to=rddunlap@osdl.org \
--cc=cmrivera@ufl.edu \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®