Automated adoption of devkit-power latencies
pknirsch at redhat.com
Tue Nov 11 07:17:21 PST 2008
Richard Hughes wrote:
> On Tue, 2008-11-11 at 14:53 +0100, Phil Knirsch wrote:
>> Using monitoring information e.g. from collectd or other sources this
>> could automatically be detected though and then the system could be
>> automatically transitioned into a related power saving states depending
>> on the load.
> What's doing the monitoring? Or is this policy from something like cron
> or IPA?
See above. Something like collectd could be used as a source for that
>> I'd personally like to use devkit-power and it's API as a service, as
>> overloading it with such functionality might very quickly lead to the
>> problems we've seen in the past with HAL where everything was put into
>> a single service.
> No, I think it's 100% on topic for DK-p. Powersaving is inextricably
> linked to latency in my opinion.
What about cases where you want to completely shut down a device though
as you know it's not used?
Philipp Knirsch | Tel.: +49-711-96437-470
Team Lead Core Services | Fax.: +49-711-96437-111
Red Hat GmbH | Email: Phil Knirsch <pknirsch at redhat.com>
Hauptstaetterstr. 58 | Web: http://www.redhat.com/
D-70178 Stuttgart, Germany
Motd: You're only jealous cos the little penguins are talking to me.
More information about the devkit-devel