Date: Sun, 18 Jul 2010 15:53:36 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Doug Barton <dougb@freebsd.org> Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org, Rui Paulo <rpaulo@freebsd.org> Subject: Re: Why is intr taking up so much cpu? Message-ID: <20100718205336.GJ5485@dan.emsphone.com> In-Reply-To: <20100718202338.GI5485@dan.emsphone.com> References: <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> <4C435CBE.50500@FreeBSD.org> <20100718202338.GI5485@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 18), Dan Nelson said: > In the last episode (Jul 18), Doug Barton said: > > 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! > > You can also use dtrace to get a count of callouts and their time spent. > Run this for a few seconds then hit ^C: That may actually be too verbose (you'll get a histogram per callout). Try the ones at http://wiki.freebsd.org/DTrace/Examples instead. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100718205336.GJ5485>