Ted Unangst wrote:
> > i'd like to
> > know where/if it works, what messages get printed, and if hw.setperf
> > does anything useful. md5 -t with setperf=0 and 100 would be nice.
>
> thanks all. there's some newer code in cvs now..
It works much better for me now. I can now play with sysctl hw.setperf
without freezing the system.
The first time I touch hw.setperf, I'm getting the follewing response:
# sysctl hw.setperf
hw.setperf=100
# sysctl hw.setperf=0
sysctl: hw.setperf: Operation not permitted
The secound time I get this response:
#sysctl hw.setperf=0
hw.setperf: 0 -> 0
and the system becomes slower and cooler.
md5 -t, time before: Time = 0.494368 seconds
md5 -t, time after: Time = 0.890196 seconds
Even though I get the expected response,
#sysctl hw.setperf=100
hw.setperf: 0 -> 100
when I try to change back to full speed, the system continues to run
"slowly and cool".
Btw. should these reports be kept offlist, and if so, whom should I
mail, tedu@ or Gordon Klok ?
-----
(dmesg.boot.old is the dmesg from my previous mail)
--- dmesg.boot.old Thu Oct 27 20:39:11 2005
+++ dmesg.boot Sat Oct 29 20:50:04 2005
@@ -1,11 +1,11 @@
-OpenBSD 3.8-current (GENERIC) #218: Thu Oct 27 04:13:58 MDT 2005
+OpenBSD 3.8-current (GENERIC) #222: Fri Oct 28 15:43:43 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(tm) 64 Processor 3000+ ("AuthenticAMD" 686-class,
512KB L2 cache) 1.81 GHz cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3
cpu0: AMD Powernow: TS FID VID TTP TM STC -cpu0: AMD Cool`n'Quiet K8: 0
available states +cpu0: AMD Cool`n'Quiet K8: 2 available states
real mem = 536125440 (523560K)
-avail mem = 482324480 (471020K)
+avail mem = 482320384 (471016K)
using 4278 buffers containing 26910720 bytes (26280K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 05/19/05, BIOS32 rev. 0 @
0xf0010
--
Jonathan Fromer
