9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] common number of interrups/sec
Date: Mon,  8 Mar 2010 11:21:31 -0500	[thread overview]
Message-ID: <e2fde92f0c955622a6013c4884870f73@coraid.com> (raw)
In-Reply-To: <a560a5d01003080804t5e58b48dyadf04bc77219af55@mail.gmail.com>

> my system is doing practically nothing. All 'stats' graphs are low
> with the exception of 'i'. I'm having like 1600 interrups per second
> (so I see a number instead of just the graph). Is this normal? How can
> I tell what those interrupts are?

if you are running 9atom, /dev/irqalloc 3rd column is the number
of interrupts for that interrupt entry.  note that if two irq handlers
are chained off the same vector, an interrupt for either will increment
both of their total counts.  this is just a hardware limitation.

- erik



  reply	other threads:[~2010-03-08 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 16:04 Rudolf Sykora
2010-03-08 16:21 ` erik quanstrom [this message]
2010-03-08 16:38   ` Rudolf Sykora
2010-03-08 16:49     ` erik quanstrom
2010-03-08 16:51       ` Rudolf Sykora
2010-03-08 16:27 ` ron minnich

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=e2fde92f0c955622a6013c4884870f73@coraid.com \
    --to=quanstro@labs.coraid.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).