From owner-freebsd-current@FreeBSD.ORG  Tue Jul 20 06:05:30 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 C9FA61065676
	for <freebsd-current@freebsd.org>; Tue, 20 Jul 2010 06:05:30 +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 501C78FC1B
	for <freebsd-current@freebsd.org>; Tue, 20 Jul 2010 06:05:30 +0000 (UTC)
Received: (qmail 11895 invoked by uid 399); 20 Jul 2010 06:05:29 -0000
Received: from localhost (HELO laptop.dougb.net)
	(dougb@dougbarton.us@127.0.0.1)
	by localhost with ESMTPAM; 20 Jul 2010 06:05:29 -0000
X-Originating-IP: 127.0.0.1
X-Sender: dougb@dougbarton.us
Date: Mon, 19 Jul 2010 23:05:26 -0700 (PDT)
From: Doug Barton <dougb@FreeBSD.org>
To: Kostik Belousov <kostikbel@gmail.com>
In-Reply-To: <20100718194109.GU2381@deviant.kiev.zoral.com.ua>
Message-ID: <alpine.BSF.2.00.1007192302300.1725@qbhto.arg>
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>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
X-message-flag: Outlook -- Not just for spreading viruses anymore!
OpenPGP: id=1A1ABC84
Organization: http://SupersetSolutions.com/
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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: Tue, 20 Jul 2010 06:05:30 -0000

On Sun, 18 Jul 2010, 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.

Ok, I thought I was going to be able to do this easily but I didn't 
realize that the numbers in the second column were thread ids, and I 
don't know how to "correlate the clock thread tid with the backtrace." 
Can you give me a hint? :)


Doug

-- 

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

 	Computers are useless. They can only give you answers.
 			-- Pablo Picasso