Date: Fri, 15 Mar 2002 10:27:22 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Josh Paetzel <friar_josh@webwarrior.net> Cc: Matthew Emmerton <matt@gsicomp.on.ca>, hackers@FreeBSD.ORG Subject: Re: Interesting sysctl variables in Mac OS X with hw info Message-ID: <3C923D0A.2259D49F@mindspring.com> References: <Pine.BSF.4.21.0203131636280.70491-100000@InterJet.elischer.org> <006601c1cb06$b9f07370$1200a8c0@gsicomp.on.ca> <3C902B36.4D4EB8E@mindspring.com> <20020315100853.P287@twincat.vladsempire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Josh Paetzel wrote: > This is a perfect example of, "Just because you can do something, > doesn't mean you should." > > I wouldn't see anything wrong with grabbing the clock frequency of the > first cpu in the system and noting in the man page that if you have > multiple cpus and you aren't running them at the same frequency, then > the reported value is applicable only to the first cpu. > > This would save a ton of time in implementing Jordan's ideas, at the > cost of not being able to deal correctlywith a situation that > (hopefully) isn't too common in the field. The other less tangible > disadvantage to my suggestion is that it takes us one step further in our > single-cpu-centric userland, ala top, uptime, and so forth only > displaying stats for "one" cpu. Incorrect information is always worse than no information. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C923D0A.2259D49F>