From owner-freebsd-bugs  Sun Feb  9 13: 0:30 2003
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7251937B401
	for <freebsd-bugs@hub.freebsd.org>; Sun,  9 Feb 2003 13:00:29 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 21C0543F75
	for <freebsd-bugs@hub.freebsd.org>; Sun,  9 Feb 2003 13:00:29 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h19L0SNS022408
	for <freebsd-bugs@freefall.freebsd.org>; Sun, 9 Feb 2003 13:00:28 -0800 (PST)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h19L0SEA022402;
	Sun, 9 Feb 2003 13:00:28 -0800 (PST)
Date: Sun, 9 Feb 2003 13:00:28 -0800 (PST)
Message-Id: <200302092100.h19L0SEA022402@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Colin Percival <colin.percival@wadham.ox.ac.uk>
Subject: Re: bin/47235: top reports inaccurate cpu usage
Reply-To: Colin Percival <colin.percival@wadham.ox.ac.uk>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR bin/47235; it has been noted by GNATS.

From: Colin Percival <colin.percival@wadham.ox.ac.uk>
To: freebsd-gnats-submit@FreeBSD.org, killing@multiplay.co.uk
Cc:  
Subject: Re: bin/47235: top reports inaccurate cpu usage
Date: Sun, 09 Feb 2003 20:59:03 +0000

    I'm not sure this is a bug.  If a process starts and stops during the 
 interval between top's updates, its cpu usage will be reflected in the "CPU 
 states" header, but top won't list the process (because it isn't running 
 any longer).  This shows up most often while rebuilding the world or kernel 
 due to the large number of very short-lived processes which are spawned.
    This could be fixed, I suppose, by reading the accounting files, but I 
 don't think it's worth the added complexity.
 
 Colin Percival
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message