From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] High interruptload on cpu server
References: <1435c4e71bbcd8b425de038c00040356@plan9.ucalgary.ca>
From: Matthias Teege <matthias-9fans@mteege.de>
In-Reply-To: <1435c4e71bbcd8b425de038c00040356@plan9.ucalgary.ca> (mirtchov@cpsc.ucalgary.ca's
 message of "Sun, 23 Nov 2003 08:09:54 -0700")
Message-ID: <86u14v6ljf.fsf@gic.mteege.de>
User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3.50 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 23 Nov 2003 18:29:02 +0100
Topicbox-Message-UUID: 91e22cd0-eacc-11e9-9e20-41e7f4b1d025

mirtchov@cpsc.ucalgary.ca writes:

> you can use kprof(3) to profile the kernel, usually the interrupt
> routine of the device driver for the device generating the interrupts
> will be one with a higher percentage.

Nice. First "snapshoot" looks like this.

ms	  %	sym
65830	 96.5	halt
860	  1.2	i8259isr
280	  0.4	resrcwait
280	  0.4	wbflush
150	  0.2	genrandom
150	  0.2	addclock0link
120	  0.1	syscall
80	  0.1	validname
70	  0.1	putmmu
60	  0.0	newrgrp

Halt?

Matthias