From owner-freebsd-performance@FreeBSD.ORG Tue Mar 18 13:06:56 2008 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 838161065670 for ; Tue, 18 Mar 2008 13:06:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 7F9ED8FC27 for ; Tue, 18 Mar 2008 13:06:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id BFB5E1A4D7E; Tue, 18 Mar 2008 05:48:06 -0700 (PDT) From: John Baldwin To: Robert Watson Date: Tue, 18 Mar 2008 08:45:28 -0400 User-Agent: KMail/1.9.7 References: <20080210120013.4C3D116A421@hub.freebsd.org> <47de32b3.1bbc720a.7cf0.ffff8ff1@mx.google.com> <20080318111805.W17188@fledge.watson.org> In-Reply-To: <20080318111805.W17188@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803180845.28959.jhb@freebsd.org> X-Mailman-Approved-At: Tue, 18 Mar 2008 13:11:54 +0000 Cc: freebsd-performance@freebsd.org, Aminuddin Abdullah Subject: Re: V7 High CPU Usage on swi5:+, what is this process? X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Mar 2008 13:06:56 -0000 On Tuesday 18 March 2008 07:21:23 am Robert Watson wrote: > On Mon, 17 Mar 2008, Aminuddin Abdullah wrote: > > I have just upgraded 5 of my machines to V7 from 6.3 and then realized > > that all the machines has a high CPU usage. Almost all of them using > > 80%-90% CPU with more than 8000 connections. Using previous 6.3, it only > > uses 40-50% CPU with the same kind of connections. > > > > Using top -S, I can see that swi5: +, PID 17 process is using 30% of CPU > > time. What is this process? > > > > All the machines are Intel C2D 6300 except one which is a AMD 4000+. > > > > Is this normal for V7? How do I downgrade to 6.3 if this V7 killing the > > CPU? > > '+' is used in a swi name to indicate that the names of the interrupts to > put in the thread name are too long, and the code looks like it was written > under the assumption that at least one name would fit. It sounds like in > this case, none fit. We should fix this code, but in the mean time, what > you might consider doing is hacking intr_event_update() in kern_intr.c to > print out overflowing names to the console using printf(9) so you can at > least see what they are. This is the somewhat suspect bit of code: The code is not suspect as p_comm is of fixed length. Someone just used too long of a name for a swi handler. > I've CC'd John, who might have views on what we should do about this. It > would be nice if we had a way to export information on all the interrupt > event sources, including soft ones, and their mappings to ithreads, > including swis, using sysctl. Or maybe we do already and he'll point us at > it. :-) We don't and that is what we need for a userland interrupt binding interface to make sense. -- John Baldwin