Proceedings of the 41st ACM SIGPLAN Conference on Programming Language Design and Implementation 2020
DOI: 10.1145/3385412.3385987
|View full text |Cite
|
Sign up to set email alerts
|

CARAT: a case for virtual memory through compiler- and runtime-based address translation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
11
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
6

Relationship

1
5

Authors

Journals

citations
Cited by 13 publications
(12 citation statements)
references
References 38 publications
1
11
0
Order By: Relevance
“…Other Benchmarks and Workloads: Although CARAT CAKE is not evaluated on an extremely diverse set of workloads, there is no particular reason why a CARAT system could not feasibly and efficiently run them. This is in part supported by the results from our prior paper [81], which shows a much wider range of benchmarks from NAS, PARSEC, and Mantevo. We also note that for overlapping benchmarks, the overheads presented in the original paper have actually gone down in this paper due to efforts in compiler optimization.…”
Section: Generality and Future Worksupporting
confidence: 67%
See 3 more Smart Citations
“…Other Benchmarks and Workloads: Although CARAT CAKE is not evaluated on an extremely diverse set of workloads, there is no particular reason why a CARAT system could not feasibly and efficiently run them. This is in part supported by the results from our prior paper [81], which shows a much wider range of benchmarks from NAS, PARSEC, and Mantevo. We also note that for overlapping benchmarks, the overheads presented in the original paper have actually gone down in this paper due to efforts in compiler optimization.…”
Section: Generality and Future Worksupporting
confidence: 67%
“…Suchy et al [81] argue that a modern OS running programs written in unmanaged languages can achieve performant memory management and protection without hardware support. A naive approach to purely software-based memory management and protection is, of course, destined to be horrifically slow.…”
Section: Carat Concepts and Prior Resultsmentioning
confidence: 99%
See 2 more Smart Citations
“…This can be very efficient, by avoiding translation for that region entirely, but it requires application changes, causes fragmentation in memory through requiring contiguity and is unsuitable for applications without a single distinct large region. CARAT [39] replaces paging with software management of physical memory, through a trusted compiler interface. This avoids the need of any paging hardware, at the expense of slowdown.…”
Section: Alternative Virtual-memory Translationmentioning
confidence: 99%