From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 06:50:31 2010 Return-Path: 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 955B8106566B for ; Wed, 21 Jul 2010 06:50:31 +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 35BD88FC14 for ; Wed, 21 Jul 2010 06:50:31 +0000 (UTC) Received: (qmail 3056 invoked by uid 399); 21 Jul 2010 06:50:30 -0000 Received: from localhost (HELO laptop.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 21 Jul 2010 06:50:30 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Date: Tue, 20 Jul 2010 23:50:28 -0700 (PDT) From: Doug Barton To: Dan Nelson In-Reply-To: <20100720164600.GA85770@dan.emsphone.com> Message-ID: References: <20100717192128.GM2381@deviant.kiev.zoral.com.ua> <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> <20100720164600.GA85770@dan.emsphone.com> 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: Kostik Belousov , freebsd-current@freebsd.org, Rui Paulo 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2010 06:50:31 -0000 On Tue, 20 Jul 2010, Dan Nelson wrote: > In the last episode (Jul 19), Doug Barton said: >> On Sun, 18 Jul 2010, Dan Nelson wrote: >>> You can also use dtrace to get a count of callouts and their time spent. >>> Run this for a few seconds then hit ^C: >> >> Okey dokey, here you go: >> >> http://people.freebsd.org/~dougb/normal-dtrace.txt >> http://people.freebsd.org/~dougb/bad-dtrace.txt > > I don't see any real difference between those two runs, so maybe it's not a > callout eating your CPU. How about running this for a few seconds, which > will print all the stack traces seen during the sampling period: > > dtrace -n 'profile:::profile-276hz { @pc[stack()]=count(); }' > > On an otherwise idle system, you should see most of the counts in cpu_idle, > with the remainder clustered in whatever code is eating your CPU. Ok, here's the output from the above: http://people.freebsd.org/~dougb/normal-dtrace-2.txt http://people.freebsd.org/~dougb/bad-dtrace-2.txt FYI, I updated to r210317 because mav's latest commits are clock related, and it seemed to help. The first flash video I tried to watch went all the way through and afterwards intr was around 2% cpu (normally it's in the 0.n% range). However, after killing all the stray npviewer.bin processes, and killing firefox, it went back down. It took watching several videos in a row to get it to the point where intr started running away again. 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