2017 IEEE Real-Time and Embedded Technology and Applications Symposium (RTAS) 2017
DOI: 10.1109/rtas.2017.14
|View full text |Cite
|
Sign up to set email alerts
|

Allowing Shared Libraries While Supporting Hardware Isolation in Multicore Real-Time Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2017
2017
2023
2023

Publication Types

Select...
5
3

Relationship

1
7

Authors

Journals

citations
Cited by 13 publications
(9 citation statements)
references
References 23 publications
0
9
0
Order By: Relevance
“…Additionally, applications still cross the boundaries of their colors when interacting with the OS itself. Finally, special care must be taken for applications that share dynamically linked libraries [14].…”
Section: A Coloring Strategy For Strict Partitioningmentioning
confidence: 99%
“…Additionally, applications still cross the boundaries of their colors when interacting with the OS itself. Finally, special care must be taken for applications that share dynamically linked libraries [14].…”
Section: A Coloring Strategy For Strict Partitioningmentioning
confidence: 99%
“…Researchers in [6,41,47,66] have developed coordinated allocation schemes for CPU and memory bandwidth resources, but they ignored the cache resource. Researchers in [30,31,55] considered the cache and memory bank resources but ignored the memory bandwidth resources. Researchers in [17] proposed a multi-resource allocation algorithm for real-time mixed criticality systems, which focuses on the tradeoffs of the cache allocation while considering the memory bank allocation.…”
Section: Related Workmentioning
confidence: 99%
“…OS-supported IPC. Previous work on MC 2 speci cally focused on data sharing, but took a limited view of the solution: it only supported user-level IPC using shared memory [28]. is limitation facilitates maximizing isolation, because it avoids the need for system calls or dynamic memory allocations.…”
Section: Types Of Data Sharingmentioning
confidence: 99%
“…However, shared-memory IPC is insu cient in many cases. For example, even simple message-passing systems require in-memory synchronization primitives or wait-free data structures (as the authors of [28] recommend). ese shortcomings are addressed by other IPC mechanisms such as message queues or pipes, but these mechanisms break isolation because, in addition to sharing with other tasks, they require sharing data with the OS kernel.…”
Section: Types Of Data Sharingmentioning
confidence: 99%
See 1 more Smart Citation