The Ninth International Symposium on High-Performance Computer Architecture, 2003. HPCA-9 2003. Proceedings.
DOI: 10.1109/hpca.2003.1183528
|View full text |Cite
|
Sign up to set email alerts
|

Power-aware control speculation through selective throttling

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
34
0

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 42 publications
(34 citation statements)
references
References 28 publications
0
34
0
Order By: Relevance
“…There has been work on reducing the energy consumed in the pipeline due to instruction-level speculation following a branch prediction [2,12]. However, the issues addressed are very different.…”
Section: Related Workmentioning
confidence: 99%
“…There has been work on reducing the energy consumed in the pipeline due to instruction-level speculation following a branch prediction [2,12]. However, the issues addressed are very different.…”
Section: Related Workmentioning
confidence: 99%
“…Others have focused on reducing energy consumption in predictors [Parikh et al 2002;Baniasadi and Moshovos 2002] and branch target buffer [Petrov and Orailoglu 2003;Shim et al 2005]. Confidence prediction and throttling [Aragon et al 2003] has been proposed as a way to control overspeculation to limit energy wasted on misspeculated instructions. Our proposal reduces the energy consumption in the front-end and, at the same time, improves the performance by increasing instruction fetch accuracy.…”
Section: Related Workmentioning
confidence: 99%
“…Energy is saved by not having to fetch, decode and eventually flush these potential wrong-path instructions. Many heuristics have been developed using branch confidence [2], and instruction flow metrics [4] …”
Section: Related Workmentioning
confidence: 99%
“…Although traditional instruction fetch may be unable to effectively utilize the increased execution bandwidth, the IRF allows us to often exploit the additional bandwidth when needed. This is similar in many ways to front-end throttling [28,4,2], which is a technique that seeks to reduce processor energy requirements by not aggressively fetching highly speculative instructions in regions with low instruction level parallelism (ILP). Whereas pipeline throttling actually limits the number of instructions fetched and decoded in a single cycle, the use of an IRF allows the fetch of instructions to remain constant, while supplying additional instructions to decode in regions of dense packing and high ILP.…”
Section: Introductionmentioning
confidence: 99%