linux-kernel - Re: RFC: A proposal for power capping through forced idle in the Linux Kernel

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]

Date:	Mon, 14 Dec 2009 16:36:20 -0800
From:	Salman Qazi <sqazi@...gle.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Michael Rubin <mrubin@...gle.com>,
	Taliver Heath <taliver@...gle.com>
Subject: Re: RFC: A proposal for power capping through forced idle in the 
	Linux Kernel

On Mon, Dec 14, 2009 at 4:19 PM, Arjan van de Ven <arjan@...radead.org> wrote:
> On Mon, 14 Dec 2009 15:11:47 -0800
> Salman Qazi <sqazi@...gle.com> wrote:
>
>
> I like the general idea, I have one request (that I didn't see quite in
> your explanation): Please make sure that all cpus in the system do
> their idle injection at the same time, so that memory can go into power
> saving mode as well during this time etc etc...
>

With the current interface, the forced idle percentages on the CPUs
are controlled independently.  There's a trade-off here.  If we inject
idle cycles on all the CPU at the same time, our machine
responsiveness also degrades: essentially every CPU becomes equally
bad for an interactive task to run on.  Our aim at the moment is to
try to concentrate the idle cycles on a small set of CPUs, to strive
to leave some CPUs where interactive tasks can run unhindered.  But,
given a different workload and goals the correct policy may be
different.

Simultaneously idling multiple "cores" becomes necessary in the SMT
case: as there is no point in idling a single thread, while the other
thread is running full tilt.  So, in such a case it is necessary to
idle all the threads making up the physical core.  This feature has
not been implemented yet.

I think the best approach may be to provide a way to specify the
policy from the user space.  Basically let the user decide at what
level of CPU hierarchy the forced idle percentages are specified.
Then, in the levels below, we simply inject at the same time.

>
> --
> Arjan van de Ven        Intel Open Source Technology Centre
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
>
--
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/