W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2010

RE: CPU API (Re: [sysinfo] draft ready for review)

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Wed, 6 Jan 2010 07:14:18 -0800
To: Thomas Roessler <tlr@w3.org>, Max Froumentin <maxfro@opera.com>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D312D66353B8@orsmsx501.amr.corp.intel.com>
On 6 Jan 2010, Thomas Roessler wrote:

>>> - What's our use case for *setting* CPU frequency from a Web
>>> application?
>> To be able to throttle the CPU, like those applications that allow you
>> to select between "conservative", "performance", "power saving" profiles.
> But that's typically not a feature of an individual application, and certainly not a feature of an >individual Web application.  I'm concerned that we're getting seriously confused about abstraction levels >here.

Yes typically *setting* CPU frequency is probably a global system feature such as for a system policies which control your CPU speed depending on for instance the temperature of your CPU, the amount of charge in your battery if AC is connected or not.

Dzung Tran 
Intel Corp
Received on Wednesday, 6 January 2010 15:14:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:41 UTC