01.12.2012 Views

Architecture of Computing Systems (Lecture Notes in Computer ...

Architecture of Computing Systems (Lecture Notes in Computer ...

Architecture of Computing Systems (Lecture Notes in Computer ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

44 P. Bellasi, W. Fornaciari, and D. Siorpaes<br />

Fig. 4. CPM: overhead <strong>of</strong> FSC identification and selection<br />

problem. These constra<strong>in</strong>ts are used to <strong>in</strong>validate all FSCs that violate them.<br />

The optimal feasible solution is the first one valid <strong>in</strong> the list <strong>of</strong> the ordered FSCs.<br />

In the previous example, FSC3 is <strong>in</strong>validated by the assertion <strong>of</strong> the constra<strong>in</strong>t<br />

v3 and so the optimal solution is the next one valid: FSC1.<br />

4 Experimental Results<br />

The proposed optimization model has been implemented <strong>in</strong> the “Constra<strong>in</strong>ed<br />

Power Manager” (CPM), a L<strong>in</strong>ux framework based on kernel 2.6.32. This implementation<br />

has been used as a workbench for a worst-case complexity analysis <strong>of</strong><br />

the developed optimization algorithms, us<strong>in</strong>g a demo-board with the Nomadik<br />

STn8815 MPSoC by STMicroelectronics. In this section we present: first the test<br />

results, and then a use-case to demonstrate the application <strong>of</strong> the framework <strong>in</strong><br />

a real usage scenario target<strong>in</strong>g the power and performance optimization <strong>of</strong> a<br />

multimedia mobile device.<br />

4.1 Overhead’s Evaluation<br />

We have measured the execution time <strong>of</strong> the algorithms for the identification<br />

and the selection <strong>of</strong> FSCs obta<strong>in</strong><strong>in</strong>g the results <strong>in</strong> Fig. 4. These overhead measurements<br />

refer to a 60s execution <strong>of</strong> the use-case and focus on the worst-case.<br />

This measures prove the negligible impact <strong>of</strong> the framework with respect to<br />

a system not us<strong>in</strong>g it. Indeed, the identification algorithm shows a maximum<br />

<strong>of</strong> 2.5% overhead for a quite complex system with 4096 feasible configurations,<br />

which is much more than the 415 <strong>of</strong> the considered use-case. This means that<br />

over the 60s <strong>of</strong> use-case execution, around 1.5s are devoted to the framework<br />

execution. However it should be considered that this algorithm runs just one<br />

time at system boot and can be easily replaced by a look-up table. Indeed,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!