Re: /proc/cpuinfo verbiage differ unnecessarily between ports...

Jes Sorensen (Jes.Sorensen@cern.ch)
02 Sep 1999 10:52:00 +0200


>>>>> "Vince" == Vince Weaver <weave@eng.umd.edu> writes:

Vince> well, I am an author of one of those "user-space tools" that
Vince> reads /proc/cpuinfo.

Vince> <PLUG>http://www.glue.umd.edu/~weave/vmwprod/linux_logo</PLUG>

No offence, but I must say that falls into the "my xxx is bigger than
your xxx" category of applications I mentioned in an earlier posting.

Vince> WHat would be nice would be a standard, something like this

Vince> number_of_cpus: 1
Vince> cpu_type: K6-2
Vince> cpu_manufacturer: AMD
Vince> cpu_speed: 350Mhz
Vince> bogomips: 680.2

Now you are being x86is again, for some architectures it is actually
very important to know the FPU type. On the m68k where the 68040 &
68060 implement a subset of the FPU instructions using kernel
emulation and one gets better performance by using code optimized for
the floating point instructions these CPUs provide natively.

Jes

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/