From owner-freebsd-current@FreeBSD.ORG Mon Sep 1 18:04:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BC8C106567B for ; Mon, 1 Sep 2008 18:04:21 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id 12D228FC18 for ; Mon, 1 Sep 2008 18:04:20 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so794281eyi.7 for ; Mon, 01 Sep 2008 11:04:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:organization:to:subject :date:user-agent:mime-version:content-type:content-transfer-encoding :message-id; bh=W4AlWK3GXZNw3w8I/fsjeeaxlkiceN4tn+3+RSMu0ms=; b=bGOT9Yp1J7SHxu3lMWfK0ZnPOJvuOl/f7V/kJQMtLqcfukUXcQviXjyod+c75xymN+ tNx3w7B/5ajC54GX394NeEe/+Y3fgvuP/AGAXXMNr6ST43/Ieo+BhsXa9mBzSIwmXbD0 gtGQ2N2ciD320U3bxSvi1eqlClbY7TiFR/Z3Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:organization:to:subject:date:user-agent:mime-version :content-type:content-transfer-encoding:message-id; b=ak4nEs+t9dm0Vv8c3MNaCsBlqV5LnQMaO2EeW4IDbXLJBOODpjC3XZCox72AJfM9+3 DCWqbDspwzWq/BOO2hD92bCtBAWsNsDKOxsCH8uz3eVsLvwKzbfphjgdngRFNoX1D8rM 9gZpz6z9jewDvLCT0KlwzFvo0wyZm+daphAsc= Received: by 10.210.90.10 with SMTP id n10mr6862523ebb.115.1220292259754; Mon, 01 Sep 2008 11:04:19 -0700 (PDT) Received: from ?0.0.0.0? ( [196.34.241.123]) by mx.google.com with ESMTPS id f13sm14199590gvd.10.2008.09.01.11.04.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 01 Sep 2008 11:04:18 -0700 (PDT) From: David Naylor Organization: Private To: freebsd-current@freebsd.org Date: Mon, 1 Sep 2008 19:21:36 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2707132.nVE3c2aNbb"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200809011921.40737.naylor.b.david@gmail.com> X-Mailman-Approved-At: Tue, 02 Sep 2008 02:41:04 +0000 Subject: powerd and multicore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2008 18:04:21 -0000 --nextPart2707132.nVE3c2aNbb Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, The way I understand powerd works by default is that it monitors the CPU us= age=20 (or idleness) and changes the CPU frequency accordingly. The default value= s=20 are >95% idle =3D> decrease frequency; <65% idle =3D> increase frequency. = =20 The problem arises when you have a system with 4 or more 'cores'. In this= =20 case the first CPU can be running flat out but still report an overall=20 idleness of 75% and thus the frequency is not increased even though the fir= st=20 core could easily be stuck, at say 200 when capable of 2400. =20 Should powerd be changed to look at CPU specific usage and adjust according= ly=20 or scale the above defaults according to the number of CPU's. =20 =46urthermore, currently (with core 2) all CPU's are controlled using a sin= gle=20 value however (I think) it is possible to have each CPU running on a=20 different frequency (and at least with some other architectures). Does=20 powerd handle these cases? Regards=20 David P.S. sysctl dev.cpu.0.freq=3D2400 complains about an invalid argument yet=20 adjusts the value accordingly. Is this know or should I file a PR. =20 P.P.S. Should the above be filed as a PR? P.P.P.S. Willing to test patches :-) P.P.P.P.S. This is the last one :-> --nextPart2707132.nVE3c2aNbb Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBIvCSkUaaFgP9pFrIRAo+WAJ9kaje0g3R7sMy6GcYmnaiUgM/HiwCeK1rs lP+P3/k/5pJG06CIzmIkDpY= =vgYM -----END PGP SIGNATURE----- --nextPart2707132.nVE3c2aNbb--