From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: David Presotto To: 9fans@cse.psu.edu Subject: Re: [9fans] High interruptload on cpu server In-Reply-To: <864qws376f.fsf@gic.mteege.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-ikczqchuzawczxwwvscnqjognd" Date: Tue, 25 Nov 2003 08:41:28 -0500 Topicbox-Message-UUID: 9342f712-eacc-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-ikczqchuzawczxwwvscnqjognd Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Depends on what you mean by kill. Just removing the file from /rc/bin/service shouldn't be a problem. Listen will fork and exec it, and the exec will just die. Could you just probe one service at a time and see what's fixing your interrupt load? --upas-ikczqchuzawczxwwvscnqjognd Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Tue Nov 25 08:36:34 EST 2003 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Tue Nov 25 08:36:32 EST 2003 Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id C93AB19B62; Tue, 25 Nov 2003 08:36:27 -0500 (EST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.18.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 5112B19B1A; Tue, 25 Nov 2003 08:36:13 -0500 (EST) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id 789EC19B1A; Tue, 25 Nov 2003 08:35:28 -0500 (EST) Received: from one.mteege.de (one.mteege.de [81.2.131.61]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 6089F19B85 for <9fans@cse.psu.edu>; Tue, 25 Nov 2003 08:35:16 -0500 (EST) Received: (qmail 42076 invoked by uid 66); 25 Nov 2003 13:35:37 -0000 Received: (qmail 41431 invoked from network); 25 Nov 2003 13:32:24 -0000 Received: from gic.mteege.de (HELO mteege.de) (192.168.153.10) by 0 with SMTP; 25 Nov 2003 13:32:24 -0000 Received: (qmail 55471 invoked by uid 1001); 25 Nov 2003 13:32:24 -0000 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 Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu X-Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Tue, 25 Nov 2003 14:32:02 +0100 X-Spam-Status: No, hits=-2.5 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_GNUS_UA version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) 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 --upas-ikczqchuzawczxwwvscnqjognd--