当前位置: X-MOL 学术Real-Time Syst. › 论文详情
Our official English website, www.x-mol.net, welcomes your feedback! (Note: you will need to create a separate account there.)
Supporting I/O and IPC via fine-grained OS isolation for mixed-criticality real-time tasks
Real-Time Systems ( IF 1.4 ) Pub Date : 2020-06-29 , DOI: 10.1007/s11241-020-09351-2
Namhoon Kim , Stephen Tang , Nathan Otterness , James H. Anderson , F. Donelson Smith , Donald E. Porter

Efforts towards hosting safety-critical, real-time applications on multicore platforms have been stymied by a problem dubbed the “one-out-of- m ” problem: due to excessive analysis pessimism, the overall capacity of an m -core platform can easily be reduced to roughly just one core. The predominant approach for addressing this problem introduces hardware-isolation techniques that ameliorate contention experienced by tasks when accessing shared hardware components, such as DRAM memory or caches. Unfortunately, in work on such techniques, the operating system (OS), which is a key source of potential interference, has been largely ignored. Most real-time OSs do facilitate the use of a coarse-grained partitioning strategy to separate the OS from user-level tasks. However, such a strategy by itself fails to address any data sharing between the OS and tasks, such as when OS services are required for interprocess communication (IPC) or I/O. This paper presents techniques for lessening the impacts of such sharing, specifically in the context of $${\textsf {MC}}^{\textsf {2}}$$ MC 2 , a hardware-isolation framework designed for mixed-criticality systems. Additionally, it presents the results from micro-benchmark experiments and a large-scale schedulability study conducted to evaluate the efficacy of the proposed techniques and also to elucidate sharing vs. isolation tradeoffs involving the OS. This is the first paper to systematically consider such tradeoffs and consequent impacts of OS-induced sharing on the one-out-of- m problem.

中文翻译:

通过细粒度操作系统隔离支持 I/O 和 IPC,用于混合关键实时任务

在多核平台上托管安全关键的实时应用程序的努力受到了一个被称为“one-of-m”问题的阻碍:由于过度的分析悲观主义,m 核平台的整体容量很容易减少到大约只有一个核心。解决此问题的主要方法引入了硬件隔离技术,该技术可改善任务在访问共享硬件组件(例如 DRAM 内存或缓存)时遇到的争用问题。不幸的是,在此类技术的研究中,作为潜在干扰的主要来源的操作系统 (OS) 在很大程度上被忽略了。大多数实时操作系统确实有助于使用粗粒度分区策略将操作系统与用户级任务分开。然而,这种策略本身无法解决操作系统和任务之间的任何数据共享问题,例如当进程间通信 (IPC) 或 I/O 需要操作系统服务时。本文介绍了减少这种共享影响的技术,特别是在 $${\textsf {MC}}^{\textsf {2}}$$ MC 2 的上下文中,这是一个为混合临界系统设计的硬件隔离框架. 此外,它还介绍了微基准实验和大规模可调度性研究的结果,以评估所提出技术的功效,并阐明涉及操作系统的共享与隔离权衡。这是第一篇系统地考虑 OS 引起的共享对 one-of-m 问题的权衡和随之而来的影响的论文。本文介绍了减少这种共享影响的技术,特别是在 $${\textsf {MC}}^{\textsf {2}}$$ MC 2 的上下文中,这是一个为混合临界系统设计的硬件隔离框架. 此外,它还介绍了微基准实验和大规模可调度性研究的结果,以评估所提出技术的功效,并阐明涉及操作系统的共享与隔离权衡。这是第一篇系统地考虑 OS 引起的共享对 one-of-m 问题的权衡和随之而来的影响的论文。本文介绍了减少这种共享影响的技术,特别是在 $${\textsf {MC}}^{\textsf {2}}$$ MC 2 的上下文中,这是一个为混合临界系统设计的硬件隔离框架. 此外,它还介绍了微基准实验和大规模可调度性研究的结果,以评估所提出技术的功效,并阐明涉及操作系统的共享与隔离权衡。这是第一篇系统地考虑 OS 引起的共享对 one-of-m 问题的权衡和随之而来的影响的论文。它展示了微基准实验和大规模可调度性研究的结果,以评估所提出技术的功效,并阐明涉及操作系统的共享与隔离权衡。这是第一篇系统地考虑 OS 引起的共享对 one-of-m 问题的权衡和随之而来的影响的论文。它展示了微基准实验和大规模可调度性研究的结果,以评估所提出技术的功效,并阐明涉及操作系统的共享与隔离权衡。这是第一篇系统地考虑 OS 引起的共享对 one-of-m 问题的权衡和随之而来的影响的论文。
更新日期:2020-06-29
down
wechat
bug