|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Dongkun Shin, Hojun Shim, Yongsoo Joo, Han-Saem Yun, Jihong Kim, Naehyuck Chang, "Energy-Monitoring Tool for Low-Power Embedded Programs," IEEE Design & Test of Computers, vol. 19, no. 4, pp. 7-17, July/August, 2002. | |||
| BibTex | x | ||
| @article{ 10.1109/MDT.2002.1018129, author = {Dongkun Shin and Hojun Shim and Yongsoo Joo and Han-Saem Yun and Jihong Kim and Naehyuck Chang}, title = {Energy-Monitoring Tool for Low-Power Embedded Programs}, journal ={IEEE Design & Test of Computers}, volume = {19}, number = {4}, issn = {0740-7475}, year = {2002}, pages = {7-17}, doi = {http://doi.ieeecomputersociety.org/10.1109/MDT.2002.1018129}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Design & Test of Computers TI - Energy-Monitoring Tool for Low-Power Embedded Programs IS - 4 SN - 0740-7475 SP7 EP17 EPD - 7-17 A1 - Dongkun Shin, A1 - Hojun Shim, A1 - Yongsoo Joo, A1 - Han-Saem Yun, A1 - Jihong Kim, A1 - Naehyuck Chang, PY - 2002 VL - 19 JA - IEEE Design & Test of Computers ER - | |||
Designing cost sensitive embedded products such as cellular phones and portable media players requires maximizing a platform?s performance while minimizing energy use. For example, if two software implementations of an MPEG-4 decoder perform quite differently on the same target platform, clearly the more efficient version will result in a more cost-effective product. Developing efficient embedded software requires a wide range of knowledge and skills. Programmers must have a good understanding not only of the target algorithms and target processor?s intricacies, but also of a program?s overall performance behavior. For example, if a program execution incurs extra performance overheads from resource conflicts, such as conflict cache misses, programmers should identify and eliminate the problems for maximum performance. In addition, programmers should be able to remove hot spots that could degrade a program?s overall perfomance.