2016 IEEE Real-Time Systems Symposium (RTSS) 2016
DOI: 10.1109/rtss.2016.015
|View full text |Cite
|
Sign up to set email alerts
|

Reconciling the Tension Between Hardware Isolation and Data Sharing in Mixed-Criticality, Multicore Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
18
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 39 publications
(18 citation statements)
references
References 25 publications
0
18
0
Order By: Relevance
“…data sharing) tasks are becoming evidently ill-suited as they diminish the performance gains of MPSoCs due to the aforementioned three limitations. Accordingly, researchers recognized that in order to have any practical impact, scheduling techniques must permit data sharing [24], [28] and the following two approaches are recently proposed to solve data sharing problems without enforcing isolation.…”
Section: Shared Resources: Shared Datamentioning
confidence: 99%
“…data sharing) tasks are becoming evidently ill-suited as they diminish the performance gains of MPSoCs due to the aforementioned three limitations. Accordingly, researchers recognized that in order to have any practical impact, scheduling techniques must permit data sharing [24], [28] and the following two approaches are recently proposed to solve data sharing problems without enforcing isolation.…”
Section: Shared Resources: Shared Datamentioning
confidence: 99%
“…Convert YUV forma ed image to a grayscale image. results concerning user-level sharing reported in [10]. CL is the best choice if the LLC is large enough to hold all message bu ers.…”
Section: Yuv2graymentioning
confidence: 99%
“…e intent of our study is not to delve into complicated precedence-related schedulability issues but rather to demonstrate the e ects of DRAM and LLC allocation policies. To avoid such complications, we assumed that tasks that communicate via IPC share a common period, like in prior work on user-level IPC in MC 2 [10]. For similar reasons, we assumed that I/O-consuming Level-A/B tasks simply poll for I/O data (polling is not necessary for Level-C tasks because they are sporadic).…”
Section: Approachmentioning
confidence: 99%
See 2 more Smart Citations