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]

Message-ID: <876389xhuk.fsf@basil.nowhere.org>
Date:	Tue, 15 Dec 2009 00:21:07 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Salman Qazi <sqazi@...gle.com>
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>, lenb@...nel.org
Subject: Re: RFC: A proposal for power capping through forced idle in the Linux  Kernel

Salman Qazi <sqazi@...gle.com> writes:
>
> We'd like to get as much of our stuff upstream as we can.  Given that
> this is a somewhat sizable chunk of work, it would be impolite of me
> to just send out a bunch of patches without hearing the concerns of
> the community.  What are your thoughts on our design and what do we
> need to change to get this to be more acceptable to the community?  I
> also would like to know if there are any existing pieces of
> infrastructure that this can utilize.

There were a lot of discussions on this a few months ago in context
of the ACPI 4 "power aggregator" which is a similar (perhaps
slightly less sophisticated) concept. 

While there was a lot of talk about teaching the scheduler about this 
the end result was just a driver which just starts real time threads
and then idles in them. This is in current mainline.

It might be a good idea to review these discussions in the archives.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/