From owner-freebsd-hackers Mon Mar 13 15:30:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C5E1E37B554; Mon, 13 Mar 2000 15:30:06 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA125102; Mon, 13 Mar 2000 18:29:33 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <16178.952891246@zippy.cdrom.com> References: <16178.952891246@zippy.cdrom.com> Date: Mon, 13 Mar 2000 18:30:08 -0500 To: "Jordan K. Hubbard" , Andrzej Bialecki From: Garance A Drosihn Subject: Re: Getting CPU usage in FreeBSD Cc: Kris Kennaway , freebsd-hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:00 PM -0800 3/12/00, Jordan K. Hubbard wrote: > > I'm definitely for it... If I can get permission from Jordan, > > perhaps the attached patches can make it into upcoming release. > >I think it's a fine idea, I'm just not sure one day before release >is the time to be talking about it. It should have been raised >before now. :( This should probably wait until we've had a little more time to think about it. The original requester mentioned: I am using FreeBSD-3.4-RELEASE/i386 for development, and would like to code to be portable for the widest range of FreeBSD versions possible. Even if we did get this in for 4.0-release, it would only solve the problem for 4.0-release. I realize that would be nice, but I have the feeling that it could wait until post-4.0-release. (I should note that I would personally like to see a per-CPU value, for those of us who have multiple-cpu systems...) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message