Sergey Babkin wrote:
> Terry Lambert wrote:
> >
> > It got really bogged down when someone pointed out that
> > they were running CPUs with different clock rates in their
> > SMP box, just to see what the net effect would be. THe
>
> As far as I understand, you just physically can't do it:
> t
Terry Lambert wrote:
>
> It got really bogged down when someone pointed out that
> they were running CPUs with different clock rates in their
> SMP box, just to see what the net effect would be. THe
As far as I understand, you just physically can't do it:
the P-II CPU initialization depends on
On Fri, Mar 15, 2002 at 10:27:22AM -0800, Terry Lambert wrote:
> 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 n
:Doug White wrote:
:> I've been asked several times about how to get CPU speed information for
:> inventory purposes.
:>
:> People would really like the speed number printed on the chip, not what
:> it's currently running at, if that's retrievable :)
:
:Can't mask the speed number.
:
:Chips with
Doug White wrote:
> I've been asked several times about how to get CPU speed information for
> inventory purposes.
>
> People would really like the speed number printed on the chip, not what
> it's currently running at, if that's retrievable :)
Can't mask the speed number.
Chips with a lower pr
On Thu, 14 Mar 2002, Jordan Hubbard wrote:
> > What for? You haven't caught the Megahertz bug too, have you? 8)
>
> I'm not supposed to focus on Megahertz, I work for Apple, but various
> benchmarking folks also like to be able to print stats like this out
> on their comparison charts and it see
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 runni
On Fri, Mar 15, 2002 at 10:08:53AM +, 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 y
On Wed, Mar 13, 2002 at 08:46:46PM -0800, Terry Lambert wrote:
> Matthew Emmerton wrote:
> > > > > This was actually discussed a while back (a month or two ago).
> > > > >
> > > > > It got really bogged down when someone pointed out that
> > > > > they were running CPUs with different clock rates
--- Jordan Hubbard <[EMAIL PROTECTED]> wrote:
> I'm not supposed to focus on Megahertz, I work for Apple, but various
> benchmarking folks also like to be able to print stats like this out
> on their comparison charts and it seems a lot easier than grepping
> /var/run/dmesg.boot. :)
I personally
> What for? You haven't caught the Megahertz bug too, have you? 8)
I'm not supposed to focus on Megahertz, I work for Apple, but various
benchmarking folks also like to be able to print stats like this out
on their comparison charts and it seems a lot easier than grepping
/var/run/dmesg.boot. :)
On Thu, 14 Mar 2002, Michael Smith wrote:
> > hw.busfrequency = 133326902
>
> Not typically obtainable. And which bus?
This is available for ia64. I think the speed returned by ia64 firmware
for this is the FSB speed.
>
> > hw.cpufrequency = 66700
>
> Should be obtainable on Alpha and Spar
> hw.busfrequency = 133326902
Not typically obtainable. And which bus?
> hw.cpufrequency = 66700
Should be obtainable on Alpha and Sparc, and calculable on x86 (though it
will probably have to be calculated at the time the sysctl is read, since
it's variable).
> hw.cachelinesize = 32
>
Matthew Emmerton wrote:
> > > > This was actually discussed a while back (a month or two ago).
> > > >
> > > > It got really bogged down when someone pointed out that
> > > > they were running CPUs with different clock rates in their
> > > > SMP box, just to see what the net effect would be. THe
> hw.busfrequency = 133326902
> hw.cpufrequency = 66700
> hw.cachelinesize = 32
> hw.l1icachesize = 32768
> hw.l1dcachesize = 32768
> hw.l2settings = -2147483648
> hw.l2cachesize = 262144
>
> Assuming that some or all of this information can be derived on x86 /
> alpha / sparc, how useful do
> On Wed, 13 Mar 2002, Brooks Davis wrote:
>
> > On Wed, Mar 13, 2002 at 04:25:00PM -0800, Terry Lambert wrote:
> > > This was actually discussed a while back (a month or two ago).
> > >
> > > It got really bogged down when someone pointed out that
> > > they were running CPUs with different clock
On Wed, 13 Mar 2002, Jordan Hubbard wrote:
> hw.busfrequency = 133326902
> hw.cpufrequency = 66700
hw.freq.{bus,cpu}
> hw.cachelinesize = 32
> hw.l1icachesize = 32768
> hw.l1dcachesize = 32768
> hw.l2settings = -2147483648
> hw.l2cachesize = 262144
hw.cache.size.line
hw.cache.size.l1.i
hw.c
Wouldn't it make the most sense to just have the
hw.cpu#
stuff you mentioned in email? That's the easiest way to understand
the data as a user at least.
Later,
George
--
George V. Neville-Neil [EMAIL PROTECTED]
Neville-Neil Consulting
On Wed, 13 Mar 2002, Brooks Davis wrote:
> On Wed, Mar 13, 2002 at 04:25:00PM -0800, Terry Lambert wrote:
> > This was actually discussed a while back (a month or two ago).
> >
> > It got really bogged down when someone pointed out that
> > they were running CPUs with different clock rates in
On Wed, Mar 13, 2002 at 04:25:00PM -0800, Terry Lambert wrote:
> This was actually discussed a while back (a month or two ago).
>
> It got really bogged down when someone pointed out that
> they were running CPUs with different clock rates in their
> SMP box, just to see what the net effect would
Alfred Perlstein wrote:
> * Jordan Hubbard <[EMAIL PROTECTED]> [020313 15:56] wrote:
[ ... ]
> > Assuming that some or all of this information can be derived on x86 /
> > alpha / sparc, how useful do folks think it would be to have this
> > information be available from sysctl space? I personally
* Jordan Hubbard <[EMAIL PROTECTED]> [020313 15:56] wrote:
> hw.busfrequency = 133326902
> hw.cpufrequency = 66700
> hw.cachelinesize = 32
> hw.l1icachesize = 32768
> hw.l1dcachesize = 32768
> hw.l2settings = -2147483648
> hw.l2cachesize = 262144
>
> Assuming that some or all of this informat
hw.busfrequency = 133326902
hw.cpufrequency = 66700
hw.cachelinesize = 32
hw.l1icachesize = 32768
hw.l1dcachesize = 32768
hw.l2settings = -2147483648
hw.l2cachesize = 262144
Assuming that some or all of this information can be derived on x86 /
alpha / sparc, how useful do folks think it would
23 matches
Mail list logo
