From owner-freebsd-ports Thu Apr 6 2:13:24 2000 Delivered-To: freebsd-ports@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 2E4F137BE90 for ; Thu, 6 Apr 2000 02:13:22 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id LAA15706; Thu, 6 Apr 2000 11:11:12 +0200 (CEST) Message-Id: <200004060911.LAA15706@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Steve Bishop Cc: Lars.Koeller@Uni-Bielefeld.DE, ports@FreeBSD.ORG Subject: Re: FreeBSD Port: xperfmon++-3.0 Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 23 Mar 2000 13:20:17 MST." <38DA7C81.14551498@veriohosting.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Apr 2000 11:11:12 +0200 From: Gary Jennejohn Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Steve Bishop writes: >After hacking up a couple of files, I was able to get xperfmon++-3.0 to compile under FreeBSD 4.0-STABLE. > >For one, I had to change line 893 to use "ad" instead of "wd". After I got >the program successfully compiled, I found that it completely uses up all >CPU time. > >I guess the timing of the interrupts for callbacks must be much too frequent. > This is very strange because I never had to touch a thing to get this working under 4.0 when it was -current (with adX disks) or under 5.0-current (with daX-disks). Maybe "wd" is no longer an alias for "ad", I don't know. I run xperfmon++ all the time and _never_ see any high CPU load as a result, even using 1 second updates. Have you tried setting the interval ? --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message