From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] High interruptload on cpu server
Date: Sun, 23 Nov 2003 12:51:08 -0500 [thread overview]
Message-ID: <1cb34c5c114ed43b9bc22061a3612578@plan9.bell-labs.com> (raw)
If you're on a PC, you can look to see how much time is
spent in interrupts by 'acid -k $pid' and dumping the
intrtimes array. Take a look at trap.c and you'll
understand. It's just an array of 20 buckets for each
possible interrupt level. Each bucket represents a
100 µ second interval. You'll be able to tell if any
one level is hogging a lot of time. I've debated adding
a user readable interface but then I'ld have to write a
man page.
kprof is moderately crappy for timing interrupts since
it samples in the clock routine which is splhi'd as
are the other interrupt routines, i.e., sampling is
mutually exclusive to the interrupt routine running.
next reply other threads:[~2003-11-23 17:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 17:51 David Presotto [this message]
2003-11-25 13:32 ` Matthias Teege
2003-11-25 13:41 ` David Presotto
2003-11-25 15:35 ` Matthias Teege
2003-11-25 15:43 ` mirtchov
2003-11-26 6:56 ` Matthias Teege
2003-11-26 8:11 ` William Josephson
2003-11-26 13:23 ` David Presotto
2003-11-26 14:13 ` mirtchov
2003-11-26 2:52 ` David Presotto
2003-11-26 6:54 ` Matthias Teege
2003-11-26 13:43 ` David Presotto
2003-11-25 16:22 ` Rob Pike
-- strict thread matches above, loose matches on Subject: below --
2003-11-23 13:38 Matthias Teege
2003-11-23 15:09 ` mirtchov
2003-11-23 17:29 ` Matthias Teege
2003-11-23 17:32 ` David Presotto
2003-11-24 4:56 ` boyd, rounin
2003-11-24 8:27 ` Fco.J.Ballesteros
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=1cb34c5c114ed43b9bc22061a3612578@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).