From owner-freebsd-current@FreeBSD.ORG Mon Aug 13 19:41:50 2007 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 8734E16A417 for ; Mon, 13 Aug 2007 19:41:50 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from host.omnisec.de (host.omnisec.de [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 0C07E13C46A for ; Mon, 13 Aug 2007 19:41:49 +0000 (UTC) (envelope-from h.schmalzbauer@omnisec.de) Received: from [192.168.1.67] (e181027114.adsl.alicedsl.de [85.181.27.114]) (authenticated bits=0) by host.omnisec.de (8.13.8/8.13.8) with ESMTP id l7DJflvY085899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Aug 2007 21:41:48 +0200 (CEST) (envelope-from h.schmalzbauer@omnisec.de) X-Authentication-Warning: smtp.dmz.omnisec.de: Host e181027114.adsl.alicedsl.de [85.181.27.114] claimed to be [192.168.1.67] From: Harald Schmalzbauer Organization: OmniSEC To: freebsd-current@freebsd.org Date: Mon, 13 Aug 2007 21:41:41 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708132141.43165.h.schmalzbauer@omnisec.de> Subject: powerd and it's "wakeup" behaviour 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, 13 Aug 2007 19:41:50 -0000 Hello, I'm using cpufreq (acpi_perf (800/9800 500/5900) with acpi_throttle and I have limited debug.cpufreq.lowest=250, so dev.cpu.0.freq_levels reads: 800/9800 700/8575 600/7350 500/5900 437/5162 375/4425 312/3687 250/2950 I haven't tested the saving which acpi_throttling provides, but I think I can gain some minutes over plain 800/500MHz(Vcore)switch. Now the problem is that "waking up" from 250 MHz to full speed needs too much time to be effective for short term task like displaying a PDF. Reading the file doesn't stress the CPU so powerd increases "clock" (paranthesized because clock has only two states, but throttling adds 6 steps) in 7 steps to 800MHz. I'd love to have a option which tells powerd to slowly step down, but jump to full throttle if threshold of cpu usage is reached, regardless the current clock setting. So a CPU usage peak would give full performance first, then slowly stepping down again according to the CPU usage. Even my old 800MHz P3-m is fast enough to complete "cpu hungry" tasks in a quiet short time, so slowly stepping clock up is not optimal form me because it's not that fast that comleting the task with quarter speed doesn't feel sluggish. Any thoughts? Anyone who could and want to implement such a feature? (my programming skills are far beyond...) Thanks, -Harry