21.01.2013 Views

Lecture Notes in Computer Science 4917

Lecture Notes in Computer Science 4917

Lecture Notes in Computer Science 4917

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.

214 N. AbouGhazaleh et al.<br />

Fig. 3. Example of positive feedback <strong>in</strong> <strong>in</strong>dependent power management <strong>in</strong> each doma<strong>in</strong><br />

at the expense of <strong>in</strong>creas<strong>in</strong>g energy consumption. These two scenarios illustrate that the<br />

<strong>in</strong>dependent policy may not properly react to a doma<strong>in</strong>’s true workload.<br />

These undesired positive feedback scenarios arise from the fact that the <strong>in</strong>dependent<br />

policy monitors only the local performance of a given doma<strong>in</strong> to set its speed. This local<br />

<strong>in</strong>formation does not identify whether the source of the load variability is local to a doma<strong>in</strong><br />

or <strong>in</strong>duced by other doma<strong>in</strong>s. As a result, the policy cannot take the correct action.<br />

In our example, the variation <strong>in</strong> IPC can be <strong>in</strong>duced by local effects such as execut<strong>in</strong>g<br />

a large number of float<strong>in</strong>g po<strong>in</strong>t <strong>in</strong>structions or suffer<strong>in</strong>g many branch mispredictions.<br />

Alternatively, effects from other doma<strong>in</strong>s such as higher memory and L2 access latency<br />

can <strong>in</strong>duce variations <strong>in</strong> IPC. Although the effect on IPC is similar, the DVS policy<br />

should behave differently <strong>in</strong> these two cases.<br />

Table 1. Percentage of time <strong>in</strong>tervals that experience positive feedback scenarios <strong>in</strong> some<br />

Mibench and SPEC2000 benchmarks<br />

adpcm dec adpcm enc basicmath crc32 gsm toast gsm untoast lame rsynth<br />

0.28% 1.73% 0.24 % 0.18% 27.7% 20.09% 22.56% 47.56%<br />

bzip equake gcc gzip parser twolf vortex vpr<br />

26.22% 13.98% 23.35 % 21.07% 26.44% 23.69% 12.38% 23.73%<br />

To f<strong>in</strong>d out how often applications experience such undesired positive feedback, we<br />

analyzed applications under Semeraro et al.’s <strong>in</strong>dependent DVS policy [3]. Table 1 illustrates<br />

the percentage of time <strong>in</strong>tervals where positive feedback occurs <strong>in</strong> some Mibench<br />

and SPEC2000 benchmarks. The data is collected over a w<strong>in</strong>dow of 500M <strong>in</strong>structions<br />

(after fast-forward<strong>in</strong>g simulations for 500M <strong>in</strong>structions). We divide the execution <strong>in</strong>to<br />

100K <strong>in</strong>struction <strong>in</strong>tervals then count the percentage of consecutive <strong>in</strong>tervals that experience<br />

positive feedback <strong>in</strong> both the CPU and L2 doma<strong>in</strong>s simultaneously. The table<br />

shows that some applications experience high rates of positive feedback, while others<br />

are largely unaffected. In the former (e.g., gsm, lame, rsynth, bzip, parser, and vpr), we<br />

expect that the <strong>in</strong>dependent policy will result <strong>in</strong> relatively high delays or high energy<br />

because it reacts with <strong>in</strong>appropriate speed sett<strong>in</strong>g for more than 20% of the time.

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

Saved successfully!

Ooh no, something went wrong!