Separating Translation from Protection in Address Spaces with Dynamic Remapping

Achermann, Reto; Dalton, Chris; Faraboschi, Paolo; Hoffmann, Moritz; Ndu, Geoffrey; Richardson, Alexander; Roscoe, Timothy; Shaw, Adrian L.; Watson, Robert N. M.

doi:10.1145/3102980.3103000

Cited by 10 publications

(9 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…• Novel architecture design: the majority of the studies involving NVM assume the use of persistent memory in two architecture models: (1) where NVM is used as storage, replacing traditional HDDs, and (2) where NVM is used as main memory, replacing partially or completely the DRAM-based main memory. In the scope of this work, it is considered that any publication that presents an architecture different from (1) and ( 2) is either proposing a new architecture or adapting an existing one and thus belongs in this category.…”

Section: Collecting and Classifying The Resultsmentioning

confidence: 99%

“…The analyzed scalability studies seek improvements on making address and protection more cache and TLB friendly, allowing systems allocated memory to grow transparently and partitioning of the entire physical address space. Besides these points, other more complex ideas are also described in studies such as decoupling protection from translation and adopting capability-based authorization [1]. At application level, object stores are usually the preferred solution for scalable storage instead of NVM file systems, for example, this is due to their flat name space and simpler structure and metadata [24] (see Section IV-A1).…”

Section: ) Cross-cutting Complementary Insightsmentioning

confidence: 99%

“…Currently, the trend in protecting PM exposed directly to the CPU seems to be switching the write permission of memory pages on and off by exploring the protection bits of page table entries and processor registers [27]. Others more recent approaches revisit capability-based systems to provide efficient fine-grained protection [1]. However, these methods do not seem organic solutions for the problem, and while some of them may incur significant overhead, others depend on hardware innovations and experimental methods.…”

Section: Memory Protectionmentioning

confidence: 99%

See 2 more Smart Citations

Non-Volatile Memory File Systems: A Survey

et al. 2019

Self Cite

View full text Add to dashboard Cite

For decades, computer architectures have treated memory and storage as separate entities. Nowadays, we watch the emergence of new memory technologies that promise to significantly change the landscape of memory systems. Byte-addressable non-volatile memory (NVM) technologies are expected to offer access latency close to that of dynamic random access memory and capacity suited for storage, resulting in storage-class memory. However, they also present some limitations, such as limited endurance and asymmetric read and write latency. Furthermore, adjusting the current hardware and software architectures to embrace these new memories in all their potential is proving to be a challenge in itself. In this paper, recent studies are analyzed to map the state-of-the-art of NVM file systems research. To achieve this goal, over 100 studies related to NVM systems were selected, analyzed, and categorized according to their topics and contributions. From the information extracted from these papers, we derive the main concerns and challenges currently being studied and discussed in the academia and industry, as well as the trends and solutions being proposed to address them.

show abstract

Section: Collecting and Classifying The Resultsmentioning

confidence: 99%

Section: ) Cross-cutting Complementary Insightsmentioning

confidence: 99%

Section: Memory Protectionmentioning

confidence: 99%

See 1 more Smart Citation

Non-Volatile Memory File Systems: A Survey

et al. 2019

Self Cite

View full text Add to dashboard Cite

show abstract

“…Putting the compatibility issues aside, spawn is considered superior to fork. A recent paper [20] reflects on the pros and cons of fork and concludes that "we should acknowledge that fork's continued existence as a first-class OS primitive holds back systems research, and deprecate it.…”

Section: Spawn Instead Of Forkmentioning

confidence: 99%

Occlum

Shen

Tian

Chen

et al. 2020

Proceedings of the Twenty-Fifth International Conference on Architectural Support for Programming Languages and Operating Syste

View full text Add to dashboard Cite

Intel Software Guard Extensions (SGX) enables user-level code to create private memory regions called enclaves, whose code and data are protected by the CPU from software and hardware attacks outside the enclaves. Recent work introduces library operating systems (LibOSes) to SGX so that legacy applications can run inside enclaves with few or even no modifications. As virtually any non-trivial application demands multiple processes, it is essential for LibOSes to support multitasking. However, none of the existing SGX LibOSes support multitasking both securely and efficiently.This paper presents Occlum, a system that enables secure and efficient multitasking on SGX. We implement the LibOS processes as SFI-Isolated Processes (SIPs). SFI is a software instrumentation technique for sandboxing untrusted modules (called domains). We design a novel SFI scheme named MPXbased, Multi-Domain SFI (MMDSFI) and leverage MMDSFI to enforce the isolation of SIPs. We also design an independent verifier to ensure the security guarantees of MMDSFI. With SIPs safely sharing the single address space of an enclave,

show abstract

“…It also configures the page tables at the memory elements with the process identifier (effectively the CR3), the virtual address, and the appropriate permissions, enabling local enforcement at the memory elements. While this mechanism is specific to proxied memory, fabric-attached memory systems have proposed a capability-based protection system to achieve similar functionality [2].…”

Section: Ddc Architecture and Resource Allocationmentioning

confidence: 99%

Disaggregation and the Application

Angel,

Nanavati,

Sen

2019

Preprint

View full text Add to dashboard Cite

This paper examines disaggregated data center architectures from the perspective of the applications that would run on these data centers, and challenges the abstractions that have been proposed to date. In particular, we argue that operating systems for disaggregated data centers should not abstract disaggregated hardware resources, such as memory, compute, and storage away from applications, but should instead give them information about, and control over, these resources. To this end, we propose additional OS abstractions and interfaces for disaggregation and show how they can improve data transfer in data parallel frameworks and speed up failure recovery in replicated, fault-tolerant applications. This paper studies the technical challenges in providing applications with this additional functionality and advances several preliminary proposals to overcome these challenges.

show abstract

Separating Translation from Protection in Address Spaces with Dynamic Remapping

Cited by 10 publications

References 17 publications

Non-Volatile Memory File Systems: A Survey

Non-Volatile Memory File Systems: A Survey

Occlum

Disaggregation and the Application

Contact Info

Product

Resources

About