From owner-freebsd-current@FreeBSD.ORG  Sun Jul 18 19:57:52 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id EF3951065670
	for <freebsd-current@freebsd.org>; Sun, 18 Jul 2010 19:57:52 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4])
	by mx1.freebsd.org (Postfix) with ESMTP id 76FC28FC0A
	for <freebsd-current@freebsd.org>; Sun, 18 Jul 2010 19:57:52 +0000 (UTC)
Received: (qmail 20447 invoked by uid 399); 18 Jul 2010 19:57:51 -0000
Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1)
	by localhost with ESMTPAM; 18 Jul 2010 19:57:51 -0000
X-Originating-IP: 127.0.0.1
X-Sender: dougb@dougbarton.us
Message-ID: <4C435CBE.50500@FreeBSD.org>
Date: Sun, 18 Jul 2010 12:57:50 -0700
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
	rv:1.9.1.10) Gecko/20100718 Thunderbird/3.0.5
MIME-Version: 1.0
To: Kostik Belousov <kostikbel@gmail.com>
References: <alpine.BSF.2.00.1007170013191.7378@qbhto.arg>
	<A81B337F-5932-44B1-BDB4-D9DD36332A16@lavabit.com>
	<alpine.BSF.2.00.1007171103060.1546@qbhto.arg>
	<F653FF83-D9CF-42A2-AE9A-B8F914090065@FreeBSD.org>
	<alpine.BSF.2.00.1007171208010.1538@qbhto.arg>
	<20100717192128.GM2381@deviant.kiev.zoral.com.ua>
	<alpine.BSF.2.00.1007180113370.1707@qbhto.arg>
	<20100718103003.GO2381@deviant.kiev.zoral.com.ua>
	<4C43541C.3060101@FreeBSD.org>
	<20100718194109.GU2381@deviant.kiev.zoral.com.ua>
In-Reply-To: <20100718194109.GU2381@deviant.kiev.zoral.com.ua>
X-Enigmail-Version: 1.0.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org, Rui Paulo <rpaulo@freebsd.org>
Subject: Re: Why is intr taking up so much cpu?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Jul 2010 19:57:53 -0000

On 07/18/10 12:41, Kostik Belousov wrote:
> When intr time starts accumulating again, try to do
> "procstat -kk <intr process pid>" and correlate the clock thread tid
> with the backtrace. Might be, it helps to guess what callouts are eating
> the CPU.

Will do, thanks!


Doug

-- 

	... and that's just a little bit of history repeating.
			-- Propellerheads

	Improve the effectiveness of your Internet presence with
	a domain name makeover!    http://SupersetSolutions.com/