From owner-freebsd-sparc64@FreeBSD.ORG Wed Jan 7 00:33:04 2009 Return-Path: Delivered-To: freebsd-sparc64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8396C1065679 for ; Wed, 7 Jan 2009 00:33:04 +0000 (UTC) (envelope-from craig001@lerwick.hopto.org) Received: from lerwick.hopto.org (81-178-20-70.dsl.pipex.com [81.178.20.70]) by mx1.freebsd.org (Postfix) with SMTP id B11508FC19 for ; Wed, 7 Jan 2009 00:33:03 +0000 (UTC) (envelope-from craig001@lerwick.hopto.org) Received: (qmail 75149 invoked by uid 98); 7 Jan 2009 00:31:42 +0000 Received: from 192.168.0.2 by polaris.lerwick.hopto.org (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.88.4/1789. hbedv: 7.1.1.11/6.35.1.178. f-prot: 4.6.6/3.16.14. spamassassin: 3.1.4. Clear:RC:1(192.168.0.2):. Processed in 5.192816 secs); 07 Jan 2009 00:31:42 -0000 Received: from main.lerwick.hopto.org (HELO ?192.168.0.2?) (192.168.0.2) by lerwick.hopto.org with SMTP; 7 Jan 2009 00:31:37 +0000 From: Craig Butler To: freebsd-sparc64@FreeBSD.org In-Reply-To: <200901062120.n06LK6cq079473@freefall.freebsd.org> References: <200901062120.n06LK6cq079473@freefall.freebsd.org> Content-Type: text/plain Date: Wed, 07 Jan 2009 00:31:13 +0000 Message-Id: <1231288273.83664.4.camel@main.lerwick.hopto.org> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: sparc64/119240 top has WCPU over 100% on UP system X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 00:33:05 -0000 Hi All I think its safe to shelve this PR for now, it does not appear to be a fault and I have seen the same result on other architectures, namely x86 and x64. I think its due to the way that top works the weighted average out, if its polling it over a period it could be possible to get above 100% result for WCPU. The -C flag appears to display the raw CPU usage at that point of time and does not go over 100% Thanks Craig Butler On Tue, 2009-01-06 at 21:20 +0000, Craig Butler wrote: > The following reply was made to PR sparc64/119240; it has been noted by GNATS. > > From: Craig Butler > To: bug-followup > Cc: > Subject: sparc64/119240 top has WCPU over 100% on UP system > Date: Tue, 06 Jan 2009 21:16:36 +0000 > > Hello > > I have also seen the same result on sparc64 and amd64 kit, I have > looked into it a bit on google and the general feeling is that the WCPU > (or weighted CPU) count is not all that accurate. > > A more accurate representation can be obtained by passing the -C flag > when starting top. This is for raw CPU rather than a weighted average, > on some quick tests on a V120 whilst running buildworld I have not seen > a reading above 100%. > > Kind Regards > > Craig Butler > > _______________________________________________ > freebsd-sparc64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 > To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org"