From: Chris Newton <newton@unb.ca>
To: Tim Moore <timothymoore@bigfoot.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: RE: FWD: RE: excessive interrupts on network cards
Date: Wed, 26 Sep 2001 12:41:53 -0300 [thread overview]
Message-ID: <3BB21EAF@webmail1> (raw)
Tim sent me this... and, yes, the count is much lower... looking around, I
found 'mpstat', which returns processor statistics.
From this output, I would say that procinfo has a bug in the -d and -D
options, or in the man page.
Thanks, for all the help guys, but this seems to be right, according to
mpstat anyways.
Thanks a BUNCH.
Chris
[root@phantom /root]# mpstat 1
Linux 2.4.10 (phantom.csd.unb.ca) 09/26/2001
12:29:48 PM CPU %user %nice %system %idle intr/s
12:29:49 PM all 3.00 0.00 9.50 87.50 5711.00
12:29:50 PM all 5.50 0.00 8.00 86.50 6139.00
12:29:51 PM all 2.00 0.00 11.00 87.00 5976.00
12:29:52 PM all 3.50 0.00 10.00 86.50 5744.00
12:29:53 PM all 5.50 0.00 9.00 85.50 5986.00
12:29:54 PM all 7.00 0.00 10.00 83.00 5904.00
12:29:55 PM all 5.00 0.00 6.50 88.50 5771.00
>===== Original Message From Tim Moore <timothymoore@bigfoot.com> =====
>Just for grins what does 'procinfo -DSn2' say?
>
>Chris Newton wrote:
>> ...
>> uptime: 0:07:54.17 context : 43253
>>
>> irq 0: 500 timer irq 16: 131 eth2
>> irq 1: 0 keyboard irq 20: 22266 eth0
>> irq 2: 0 cascade [4] irq 21: 0 eth1
>> irq 6: 0 irq 30: 0 aic7xxx
>> irq 12: 0 irq 31: 121 aic7xxx
>> irq 14: 0 ide0
>--
next reply other threads:[~2001-09-26 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 15:41 Chris Newton [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-25 23:19 FWD: RE: excessive interrupts on network cards Chris Newton
2001-09-25 23:58 ` Tim Moore
2001-09-25 23:04 Chris Newton
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=3BB21EAF@webmail1 \
--to=newton@unb.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=timothymoore@bigfoot.com \
/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