From owner-freebsd-current Tue Mar 27 10:22:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id CB1A037B718 for ; Tue, 27 Mar 2001 10:22:31 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2RIMAG58602; Tue, 27 Mar 2001 10:22:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200103271625.f2RGPP815322@bunrab.catwhisker.org> Date: Tue, 27 Mar 2001 10:21:45 -0800 (PST) From: John Baldwin To: David Wolfskill Subject: Re: top output broked? Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Mar-01 David Wolfskill wrote: >>Date: Tue, 27 Mar 2001 03:18:10 -0800 >>From: Alfred Perlstein > > >> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND >> 824 root -8 0 1048K 596K biord 0 0:38 0.00% 0.00% find >> 385 root 4 0 32740K 31944K select 1 0:32 0.00% 0.00% XFree86 >> 836 root -8 0 532K 276K biord 1 0:07 0.00% 0.00% nfsd >>14848 root 96 0 26912K 26832K RUN 1 0:04 0.00% 0.00% ld >> 424 bright 4 0 2120K 1340K select 0 0:04 0.00% 0.00% rxvt > > >>no cpu time, known issue? > > I get non-zero values from time to time; in particular, I fired up an > xterm & did a "while (1)" loop in it, and the CPU times increased in a > gratifying manner. :-} > > However, the usual values I'm seeing are rather lower than I would > expect, and lower than the same machine running -STABLE (within the last > several days, by my recollection). > > As a reality check, I'm trying "vmstat 5", and it's consistently > reporting either 99 or 100% idle. There -- I got both it & top to > report something noticeable: I fired up netscape.... > > Maybe it really *is* using CPU much more efficiently...? No, I didn't > think so, but it was a nice thought.... :-) > > Oh: recent CVSup history (I hadn't noticed the behavior in the > -CURRENNT I built yesterday): > > CVSup started at Sun Mar 25 23:47:00 PST 2001 > CVSup ended at Sun Mar 25 23:52:25 PST 2001 > CVSup started at Mon Mar 26 23:47:00 PST 2001 > CVSup ended at Mon Mar 26 23:53:39 PST 2001 Keep in mind that we no longer charge interrupt time to the process being interrupted, instead all that interrupt handling has been pushed off into ithreads. Same for software interrupt threads. That said, I don't see how X is so idle, it's certainly not on my laptop: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 454 john 4 0 44440K 43464K select 1:57 4.05% 4.05% XFree86 461 john 4 0 17076K 16144K select 0:35 0.39% 0.39% enlightenment 492 john 4 10 3072K 2040K select 0:28 0.10% 0.10% E-ScreenSave. 1022 john 4 0 7764K 7008K select 0:09 0.10% 0.10% xfmail 398 root 4 0 984K 564K select 0:06 0.00% 0.00% moused > Cheers, > david -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message