Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Jan 2009 10:18:30 -0500
From:      "Gabriel Lavoie" <glavoie@gmail.com>
To:        "Dmitry Kolosov" <ivakras1@gmail.com>
Cc:        freebsd-acpi@freebsd.org
Subject:   Re: EST (Enhanced Intel SpeedStep(R) Technology) on amd64
Message-ID:  <d05df8620901100718j6b89ff11s88847adacaed75d7@mail.gmail.com>
In-Reply-To: <200901101059.31131.ivakras1@gmail.com>
References:  <d05df8620901081551j5572b45aqbed51e2955efccc8@mail.gmail.com> <496780A8.7070801@root.org> <d05df8620901091200v5eba8908kda486b722f4643c9@mail.gmail.com> <200901101059.31131.ivakras1@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I have these settings in my rc.conf and /boot/loader.conf now:

/etc/rc.conf:
powerd_enable="YES"
powerd_flags="-i 90 -r 90 -p 250"

/boot/loader.conf:
hint.p4tcc.0.disabled=1
hint.p4tcc.1.disabled=1
hint.acpi_throttle.0.disabled=1
hint.acpi_throttle.1.disabled=1

This way I only have the list of frequencies EST gives and powerd will
raise/lower the frequency as soon as the load goes above/under 10%. I
also find my system to be more responsive with a polling time under
500ms. This is why I lowered it to 250ms.

I'm quite satisfied with this setup and this is what I was looking for
when I installed this server. About the settings in
/etc/default/rc.conf, I don't know where they are used...

CPU info from sysctl:
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU1
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1200
dev.cpu.0.freq_levels: 2500/88000 2000/47608 1600/44616 1200/41800
dev.cpu.0.cx_supported: C1/0
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00%
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU2
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/0
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00%
dev.acpi_perf.0.%driver: acpi_perf
dev.acpi_perf.0.%parent: cpu0
dev.acpi_perf.1.%driver: acpi_perf
dev.acpi_perf.1.%parent: cpu1
dev.est.0.%desc: Enhanced SpeedStep Frequency Control
dev.est.0.%driver: est
dev.est.0.%parent: cpu0
dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800
dev.est.1.%desc: Enhanced SpeedStep Frequency Control
dev.est.1.%driver: est
dev.est.1.%parent: cpu1
dev.est.1.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800
dev.cpufreq.0.%driver: cpufreq
dev.cpufreq.0.%parent: cpu0
dev.cpufreq.1.%driver: cpufreq
dev.cpufreq.1.%parent: cpu1

Gabriel

2009/1/10 Dmitry Kolosov <ivakras1@gmail.com>:
> On Friday 09 January 2009 23:00:03 Gabriel Lavoie wrote:
>> Another question. Any reason why powerd doesn't use
>> dev.est.0.freq_settings when it is available instead of
>> dev.cpu.0.freq_levels?
>>
>> On my system:
>> dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657
>> 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125
>> 600/20900 450/15675 300/10450 150/5225
>> dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800
>>
>> If I don't lower the polling time of powerd to 100ms, my system
>> becomes way too much unresponsive because powerd takes too much time
>> to increase the frequency, step by step and there are a lot of
>> settings with dev.est.0.freq_settings (14). With
>> dev.est.0.freq_settings, the minimal setting is high enough so the
>> system stays responsive and powerd would bring it up to max frequency
>> quickly enough, even if the polling time is still kept at 500ms. This
>> would work more like Windows or Linux where the lowest frequency at
>> which the CPU will drop is the lowest EIST gives (here 1200 MHz).
>>
>> Gabriel
>>
>> 2009/1/9 Nate Lawson <nate@root.org>:
>> > Gabriel Lavoie wrote:
>> >> My processor seems correctly recognized by est under 7.1, I get the
>> >> correct frequency/value pairs. What I would like is the automatic
>> >> behaviour where the CPU is downclocked to 50% under no load, found
>> >> under Windows/Linux and I would also like to know why estctrl isn't
>> >> supported under amd64. I already contacted Colin. :)
>> >
>> > powerd(8) is what you want. You can set an absolute frequency for idle.
>> >
>> > --
>> > Nate
>
> What this settings for in defaults/rc.conf?
> performance_cx_lowest="HIGH"    # Online CPU idle state
> performance_cpu_freq="NONE"     # Online CPU frequency
> economy_cx_lowest="HIGH"        # Offline CPU idle state
> economy_cpu_freq="NONE"         # Offline CPU frequency
>
> Im using it with powerd at the same time and it runs just smoothly.
> _______________________________________________
> freebsd-acpi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org"
>



-- 
Gabriel Lavoie
glavoie@gmail.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d05df8620901100718j6b89ff11s88847adacaed75d7>