2017
DOI: 10.1109/tpds.2016.2645219
|View full text |Cite
|
Sign up to set email alerts
|

Lightweight Virtual Memory Support for Zero-Copy Sharing of Pointer-Rich Data Structures in Heterogeneous Embedded SoCs

Abstract: While high-end heterogeneous systems are increasingly supporting heterogeneous uniform memory access (hUMA), their low-power counterparts still lack basic features like virtual memory support for accelerators. Instead of simply passing pointers, explicit data management involving copies is needed which hampers programmability and performance. In this work, we evaluate a mixed hardware/software solution for lightweight virtual memory support for many-core accelerators in heterogeneous embedded systems-on-chip. … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
18
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
4
2

Relationship

4
2

Authors

Journals

citations
Cited by 8 publications
(18 citation statements)
references
References 30 publications
(44 reference statements)
0
18
0
Order By: Relevance
“…In this field, the research community has evaluated commercial designs [17] and also proposed optimized SVM infrastructure for custom PMCA architectures [18], [19]. In our previous works, we have explored lightweight SVM support for PMCAs based on a softwaremanaged IOTLB considering applications based on regular [20] and irregular (pointer-rich) [21] memory access patterns, and exploring PMCA-local IOTLB management [22].…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…In this field, the research community has evaluated commercial designs [17] and also proposed optimized SVM infrastructure for custom PMCA architectures [18], [19]. In our previous works, we have explored lightweight SVM support for PMCAs based on a softwaremanaged IOTLB considering applications based on regular [20] and irregular (pointer-rich) [21] memory access patterns, and exploring PMCA-local IOTLB management [22].…”
Section: Related Workmentioning
confidence: 99%
“…If all TLB entries are in use, the oldest mapping is invalidated and the corresponding user-space page is unlocked (FIFO replacement). Based on the transaction attributes, the worker thread signals the hardware to repeat the transaction that previously produced a TLB miss/page fault [21].…”
Section: Shared Virtual Memory Designmentioning
confidence: 99%
See 1 more Smart Citation
“…It is comprised of a translation lookaside buffer (TLB), parallel hardware page table walkers (PTWs), transaction and data buffers, and coherent page table caches. The alternative is a hybrid hardware-software design, which consists of a TLB controlled by software (e.g., by a kernel driver on the host [6], [7] or directly by the accelerator [8]). We subsequently refer to the former class of IOMMUs as conventional and to the second class as hybrid.…”
Section: Introductionmentioning
confidence: 99%
“…In the low-end embedded SoC domain, however, SVM is not or only partially supported. Specifically, SVM solutions for HESoCs usually rely on mixed hardware-software designs, where simple input/output translation lookaside buffers (IOTLBs) used by the accelerator to translate virtual addresses are fully controlled by software (e.g., via a kernel-level driver module) [19,31].…”
Section: Introductionmentioning
confidence: 99%