Steven Roberts sent me a patch updating the various setperf thresholds.

But instead of continuing to overdocument internal behavior, provide a
high level description of the modes and their purpose.

diff --git a/usr.sbin/apmd/apmd.8 b/usr.sbin/apmd/apmd.8
index 00c3aa2..e283ff0 100644 (file)
--- a/usr.sbin/apmd/apmd.8
+++ b/usr.sbin/apmd/apmd.8
@@ -1,4 +1,4 @@
-.\"    $OpenBSD: apmd.8,v 1.43 2010/10/28 18:21:20 jmc Exp $
+.\"    $OpenBSD: apmd.8,v 1.44 2014/07/24 01:04:58 tedu Exp $
 .\"
 .\" Copyright (c) 1995 John T. Kohl
 .\" All rights reserved.
@@ -26,7 +26,7 @@
 .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: October 28 2010 $
+.Dd $Mdocdate: July 24 2014 $
 .Dt APMD 8
 .Os
 .Sh NAME
@@ -69,19 +69,10 @@ The options are as follows:
 Start
 .Nm
 in automatic performance adjustment mode.
-In this mode, when CPU idle time falls below 10%,
-or if the AC power is connected and the battery is more than 15% charged,
-or if the battery is absent,
-.Nm
-raises
-.Va hw.setperf
-to 100.
-Otherwise when CPU idle time is above 30%
-and the system is running on battery power,
-.Nm
-lowers
+Optimize for performance, but lower
 .Va hw.setperf
-as much as possible to reduce power consumption.
+when running on battery power or when AC is connected but the battery charge
+level is low.
 .It Fl a
 BIOS-initiated suspend or standby requests are
 ignored if the system is connected to line current and not running from
@@ -90,16 +81,9 @@ batteries (user requests are still honored).
 Start
 .Nm
 in cool running performance adjustment mode.
-In this mode, when CPU idle time falls below 10%,
-.Nm
-raises
-.Va hw.setperf
-as much as necessary.
-Otherwise when CPU idle time is above 30%,
-.Nm
-lowers
+Optimize for low power use by keeping
 .Va hw.setperf
-as much as possible to reduce heat, noise, and power consumption.
+low, except when CPU idle time drops and more performance is required.
 .It Fl d
 .Nm
 enters debug mode, logging to facility