* From: Jonathan Lemon <[EMAIL PROTECTED]> * What I want is a simple new readable sysctl, something like: * * hw.clockrate: 132 * * I think that this would be useful both for development (how fast * is that stupid machine down in the bunker?), and system admininstration * (who needs a cpu upgrade this year?). I like that. * Doing this for Pentium and better systems should be trivial. Doing * it for 486 and lower would just add a timing loop. Doing it for SMP * would be harder. * * hw.cpu0.clockrate: 233 * hw.cpu1.clockrate: 233 * * Possibly? The implementer gets to pick a better name than these. How about hw.clockrate.cpu0: 233 hw.clockrate.cpu1: 233 (cpu0 only for uni-procs, of course). Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
Satoshi - Ports Wraith - Asami Fri, 3 Sep 1999 00:40:26 -0700
- Re: CFD: "bogomips" CPU performan... Chris Costello
- Re: CFD: "bogomips" CPU performan... Ollivier Robert
- Re: CFD: "bogomips" CPU perf... Alfred Perlstein
- Re: CFD: "bogomips" CPU perf... Kris Kirby
- Re: CFD: "bogomips" CPU performan... Oliver Fromme
- Re: CFD: "bogomips" CPU perf... Milan Kopacka
- Re: CFD: "bogomips" CPU perf... Peter Wemm
- Re: CFD: "bogomips" CPU performan... Kurt Olsen
- Re: CFD: "bogomips" CPU perf... Jordan K. Hubbard
- Re: CFD: "bogomips" CPU performan... Jonathan Lemon
- Re: CFD: "bogomips" CPU perf... Satoshi - Ports Wraith - Asami
- Re: CFD: "bogomips" CPU ... Jeroen Ruigrok/Asmodai