From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] High interruptload on cpu server References: <1cb34c5c114ed43b9bc22061a3612578@plan9.bell-labs.com> From: Matthias Teege In-Reply-To: <1cb34c5c114ed43b9bc22061a3612578@plan9.bell-labs.com> (David Presotto's message of "Sun, 23 Nov 2003 12:51:08 -0500") Message-ID: <864qws376f.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: Tue, 25 Nov 2003 14:32:02 +0100 Topicbox-Message-UUID: 932f4ca8-eacc-11e9-9e20-41e7f4b1d025 David Presotto writes: > 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 Ok, I'll do so. I discover some nice thing. I can bring down the interrupt load to a normal level (99% idle ;-)) if I run a nmap against the cpu server. After the nmap run the interrupt load stays on that normal level. Maybe I kill a hanging service (timesync?) whit nmap. Funny. Matthias -- Matthias Teege -- http://www.mteege.de make world not war