From owner-freebsd-hardware Fri Jul 6 15:13:31 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id 94ACE37B403; Fri, 6 Jul 2001 15:13:26 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f66MQra02267; Fri, 6 Jul 2001 15:26:58 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107062226.f66MQra02267@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lars Eggert Cc: Mike Smith , Peter Pentchev , arch@freebsd.org, hardware@freebsd.org Subject: Re: New hw.cpuhz sysctl as per PR i386/27627 In-reply-to: Your message of "Fri, 06 Jul 2001 15:09:53 PDT." <3B463731.2090001@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Jul 2001 15:26:52 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Mike Smith wrote: > > > CPU speeds aren't constants; this is probably not the right place to put > > it. It also assumes there's only one CPU, which isn't acceptable. > > Being the author of the original patch, I agree that its a hack - but > it's better than nothing :-) Plus, it doesn't necessarily assume only > one CPU - it does assume they all have the same fixed speed though. It doesn't seem to serve much useful purpose; the information is already available to the user in the boot-time message buffer, and it's not useful as a number to a running process. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message