Linked by Kroc Camen on Thu 30th Sep 2010 12:12 UTC
Permalink for comment 443316
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2010-03-08
Actually, proper scheduling can make devices more power-efficient.
As an example, usual round robin algorithms run software whenever it can run, keeping the processor busy and energy-hungry as long as one task is active and it's not put in a sleep state.
A power-efficient scheduling algorithm could swap out some tasks under certain conditions, so that the processor can be put to rest more often. E.g. pausing a game when it's put in the background in order to read some mail won't hurt its functionality the tiniest bit, and CPU use during the time spent reading the mail will drop from 100% (game running in the background) to a few % (scrolling text from time to time).
Defining which tasks are swapped out can be the role of a high-level API, but as you see the ability to swap a task out and stop scheduling it must first be provided at a low level.