linux-kernel - RE: [linux-pm] [PATCH] cpuidle: avoid singing capacitors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <924EFEDD5F540B4284297C4DC59F3DEEB33CDD@orsmsx423.amr.corp.intel.com>
Date:	Thu, 13 Mar 2008 09:47:30 -0700
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	"Pierre Ossman" <drzeus-list@...eus.cx>,
	"Len Brown" <lenb@...nel.org>
Cc:	<linux-pm@...ts.linux-foundation.org>,
	"Pavel Machek" <pavel@....cz>,
	"LKML" <linux-kernel@...r.kernel.org>,
	"Adam Belay" <abelay@...ell.com>,
	"Andi Kleen" <andi@...stfloor.org>,
	"Lee Revell" <rlrevell@...-job.com>
Subject: RE: [linux-pm] [PATCH] cpuidle: avoid singing capacitors

 

>-----Original Message-----
>From: linux-kernel-owner@...r.kernel.org 
>[mailto:linux-kernel-owner@...r.kernel.org] On Behalf Of Pierre Ossman
>Sent: Thursday, March 13, 2008 9:35 AM
>To: Len Brown
>Cc: linux-pm@...ts.linux-foundation.org; Pavel Machek; LKML; 
>Adam Belay; Andi Kleen; Lee Revell
>Subject: Re: [linux-pm] [PATCH] cpuidle: avoid singing capacitors
>
>On Wed, 12 Mar 2008 15:11:17 -0400
>Len Brown <lenb@...nel.org> wrote:
>
>> > 
>> > So for now, the only viable workaround is processor.max_cstate....
>> 
>> yup, that's why we put it in.  Is it insufficient?
>> 
>
>For some value of insufficient. It is sub-optimal. I'm hoping 
>there is a way to enter C3 in a pattern that avoids the noise 
>and still gives a reduced power usage.
>

Can you try using /dev/cpu_dma_latency from an user space application.
Refer Documentation/pm_qos_interface.txt for usage. With this interface
you can change menu governor behavior from userspace, by dynamically
allowing it to use C3 or not. I am thinking that something like allowing
C3 for few seconds and blocking it for few seconds may help.

Thanks,
Venki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/