Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Jul 2010 23:05:26 -0700 (PDT)
From:      Doug Barton <dougb@FreeBSD.org>
To:        Kostik Belousov <kostikbel@gmail.com>
Cc:        freebsd-current@freebsd.org, Rui Paulo <rpaulo@freebsd.org>
Subject:   Re: Why is intr taking up so much cpu?
Message-ID:  <alpine.BSF.2.00.1007192302300.1725@qbhto.arg>
In-Reply-To: <20100718194109.GU2381@deviant.kiev.zoral.com.ua>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1007192302300.1725>