From owner-freebsd-current@FreeBSD.ORG Mon May 5 04:43:11 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7BFC8650; Mon, 5 May 2014 04:43:11 +0000 (UTC) Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 24FBB1C1A; Mon, 5 May 2014 04:43:11 +0000 (UTC) Received: by mail-qg0-f48.google.com with SMTP id i50so5758584qgf.7 for ; Sun, 04 May 2014 21:43:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=RP615p6mVa6lGiL7dg0Dgs1WshHFgZxNblI9q4aZp54=; b=LEr0pIVbTSU7D/IDncGiE6VbI7xMKdGofjMxrRuFOtRTj5gnJGjUOS3FDLguWC+tJT wa25gDg1RknT90rhYPvDOK3ATnCQ6kOZ+BNabbLNM0c032HvXceBF6df8qJhv1NrIziy B7IIeJNgT6RpQxBMBLGoXhVbjzhyvZ7/WPJ4FR+cwlCSKrW0rzdvVz5HAwH2Y4lV4cII weR6eYhsupENTbZH7JjLHK09UmB1PzMUh0siPv3aYRZDfzXcVrAQ2muKW/xF7Cdos4x+ 28JfC0/5HUYPpPlnO5LUoI+hQNzxXVJFEnXo1+NOqwUrm0lXOvb9nu95V9Ukou4JaRzm hc7A== MIME-Version: 1.0 X-Received: by 10.224.129.66 with SMTP id n2mr41818433qas.55.1399264990237; Sun, 04 May 2014 21:43:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Sun, 4 May 2014 21:43:10 -0700 (PDT) In-Reply-To: References: <3F7430D7-3C0F-43E1-8EBD-8AA4F701497C@FreeBSD.org> <20140503155745.GA2457@La-Habana> <20140503192305.GA1847@La-Habana> <20140504142839.GA9271@La-Habana> <53666102.5080205@allanjude.com> <53667352.4030807@allanjude.com> <536673ED.207@freebsd.org> Date: Sun, 4 May 2014 21:43:10 -0700 X-Google-Sender-Auth: OXQzQsyYJEje0syk9oVlViadjDs Message-ID: Subject: Re: Leaving the Desktop Market From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current , Nathan Whitehorn X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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, 05 May 2014 04:43:11 -0000 throttling is disabled now. -a On 4 May 2014 21:27, Kevin Oberman wrote: > On Sun, May 4, 2014 at 10:07 AM, Nathan Whitehorn wrote: > >> On 05/04/14 10:05, Allan Jude wrote: >> >>> On 2014-05-04 11:47, Allan Jude wrote: >>> >>>> On 2014-05-04 10:28, Matthias Apitz wrote: >>>> >>>>> El d=C3=ADa Saturday, May 03, 2014 a las 04:59:48PM -0700, Kevin Ober= man >>>>> escribi=C3=B3: >>>>> >>>>> On Sat, May 3, 2014 at 1:25 PM, Adrian Chadd >>>>>> wrote: >>>>>> >>>>>> Set it to the lowest available Cx state that you see in dev.cpu.0 . >>>>>>> >>>>>>> >>>>>>> Available is not required. Set it to C8. That guarantees that you >>>>>> will use >>>>>> the lowest available. The correct incantation in rc.conf is "Cmax". >>>>>> performance_cx_lowest=3D"Cmax" >>>>>> economy_cx_lowest=3D"Cmax" >>>>>> >>>>>> But, unless you want laggy performance, you will probably also want: >>>>>> hint.p4tcc.0.disabled=3D1 >>>>>> hint.acpi_throttle.0.disabled=3D1 >>>>>> in /boot/loader.conf. Low Cx states and TCC/throttling simply don't = mix >>>>>> well and TCC is not effective, as mentioned earlier in this thread. >>>>>> >>>>> Re/ powerd I have in /etc/rc.conf: >>>>> >>>>> # powerd >>>>> powerd_enable=3D"YES" >>>>> powerd_flags=3D"-a max -b adp" >>>>> # >>>>> performance_cx_lowest=3D"Cmax" >>>>> economy_cx_lowest=3D"Cmax" >>>>> >>>>> (and the additional hint.* in /boot/loader.conf as well). Which proce= ss >>>>> 'performance_cx_lowest' and 'economy_cx_lowest' target exactly as con= fig >>>>> values? >>>>> >>>>> Thx >>>>> >>>>> matthias >>>>> >>>>> In a pretty unscientific test on my laptop (Lenovo T530 with Intel i= 5 >>>> 3320M), setting hw.acpi.cpu.cx_lowest=3DC8 lowered power consumption a= t >>>> idle by about 3 watts, which adds about 30-45 minutes to my battery li= fe >>>> during conservative usage. >>>> >>>> Using PCBSD 10, so hint.acpi_throttle.0.disabled=3D1 was already set >>>> (apparently solves some issue with powerd on some AMD systems) >>>> >>>> I have added hint.p4tcc.0.disabled=3D1 but not sure where to expect to= see >>>> a difference. >>>> >>>> I see the difference now, with the p4tcc stuff disabled, the lowest >>> cpufreq is now 1200mhz instead of 150mhz >>> >>> >>> >> I just set the default for acpi_throttle and p4tcc in HEAD to disabled b= y >> adding these line to the default /boot/device.hints. If you want them ba= ck, >> editing your device.hints will restore them. This can be reverted if man= y >> people want throttling enabled by default, but all I have heard so far -= - >> and for the past many years -- is a unanimous chorus to turn it off. >> -Nathan >> > > Anyone playing around with Thermal Management should read the article on > Tom's Hardware on the subject. It explains things quite nicely. Even I > could understand it. :-) > http://www.tomshardware.com/reviews/cpu-cooler-fails,1695-3.html > The section on Thermal Monitor 2 was new to me as it has been added since= I > last researched this several years ago. Note the tie-in between TM2 and > EST rather than simple throttling (skipping N of every 8 clock cycles). > Section 2 of the article has thermal specs on a lot of processors, too.. > > Bottom line of the article is to make sure TM2 is enabled and just leave = it > alone to do its thing. No throttling of any sort for power mis-management= . > > The one area that can stand a close look is the algorithm for adjusting > EST. It probably will make far less difference than C-states, but it is a > legitimate power management technique and it is under the control of > powerd. Several people have suggested modification for this and I think > it's at least worth a look. > > Finally, if we don't default p4tcc and throttling to off and change the > default for C-states to Cmax, a lot of people will be very unhappy. > Disabling throttling really must come first. > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.co > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "