Proceedings of the Tenth International Symposium on Code Generation and Optimization 2012
DOI: 10.1145/2259016.2259023
|View full text |Cite
|
Sign up to set email alerts
|

WCET-aware static locking of instruction caches

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
27
0

Year Published

2013
2013
2019
2019

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 36 publications
(28 citation statements)
references
References 9 publications
1
27
0
Order By: Relevance
“…There are approaches for reducing the WCET [26], [27], but these are static. Thus, the contents in the SPM are fixed before execution and no changes occur during runtime.…”
Section: Related Workmentioning
confidence: 99%
“…There are approaches for reducing the WCET [26], [27], but these are static. Thus, the contents in the SPM are fixed before execution and no changes occur during runtime.…”
Section: Related Workmentioning
confidence: 99%
“…By carefully selecting the memory blocks for locking, WCET can be improved. There exist two locking mechanisms, static cache locking [9,19,22,16] and dynamic cache locking [5,26]. However, all of the above techniques lock the entire cache.…”
Section: Related Workmentioning
confidence: 99%
“…We compare m with the candidate memory block mblk that currently has the most utilization gain (line 20). If m has more utilization gain than mblk, we update mblk with m (line [21][22]. We continue to do this until all candidate memory blocks are considered.…”
Section: C2 Utilization Optimization Algorithmmentioning
confidence: 99%
“…Most cache locking techniques aimed at improving the WCET employ static cache locking [9], [15], [18], [7]. Static locking loads and locks the memory blocks at program startup, and the locked content remains unchanged throughout the program execution.…”
Section: Introductionmentioning
confidence: 99%
“…Static locking loads and locks the memory blocks at program startup, and the locked content remains unchanged throughout the program execution. Most static locking techniques use full cache locking [9], [15], [18] where the entire cache is locked. However, full locking does not allow the unlocked memory blocks to use the cache and exploit their locality, and thus may introduce negative impact on the overall WCET.…”
Section: Introductionmentioning
confidence: 99%