From owner-freebsd-acpi@FreeBSD.ORG  Fri Jun  5 18:00:02 2009
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 59654106564A
	for <freebsd-acpi@freebsd.org>; Fri,  5 Jun 2009 18:00:02 +0000 (UTC)
	(envelope-from ws@au.dyndns.ws)
Received: from ipmail05.adl2.internode.on.net (ipmail05.adl2.internode.on.net
	[203.16.214.145])
	by mx1.freebsd.org (Postfix) with ESMTP id D20388FC19
	for <freebsd-acpi@freebsd.org>; Fri,  5 Jun 2009 18:00:01 +0000 (UTC)
	(envelope-from ws@au.dyndns.ws)
Received: from ppp103-111.static.internode.on.net (HELO [192.168.1.244])
	([150.101.103.111])
	by ipmail05.adl2.internode.on.net with ESMTP; 06 Jun 2009 03:14:45 +0930
From: Wayne Sierke <ws@au.dyndns.ws>
To: freebsd-acpi@freebsd.org
Content-Type: text/plain
Date: Sat, 06 Jun 2009 03:14:42 +0930
Message-Id: <1244223882.24951.3369.camel@predator-ii.buffyverse>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.2 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Subject: powerd on multi-core cpus
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jun 2009 18:00:02 -0000

Hi,

I recently tried powerd for the first time and I'm wondering whether a
couple of aspects of its behaviour are considered usual.

First is that the load value displayed by powerd ranges to a maximum of
#cpus x 100%, e.g. 200% on a dual-core opteron and 400% on a dual-core
atom with Hyper-threading.

Second is that in the default adaptive mode, the 'wanted freq' ranges to
a maximum of #cores x max-freq, e.g. 3618MHz on a dual-core opteron with
a max-freq of 1809MHz, and 3236MHz on a dual-core atom with a max-freq
of 1618MHz.

These were seen with 7.2-STABLE i386. I found it somewhat
counter-intuitive since powerd rejects configuration settings for load
thresholds of more than 100%, e.g.:
# powerd -v -r 125
powerd: 125 is not a valid percent

Is this how powerd is expected to behave or is there something amiss
with my setups?


Thanks,

Wayne