Atlas: Leveraging Locks for Non-volatile Memory Consistency

Share

Abstract: Non-volatile memory, such as memristors and PCRAM, can revolutionize the way programs persist data. In-memory objects can be persistent as the program executes, thus removing the need for a separate data storage format. However, the challenge is to ensure that such data remains consistent if a failure occurs during execution. In this paper, we present Atlas, a system with durability semantics to lock-based code, typically allowing us to automatically maintain a globally consistent state even in the presence of failures. We identify failure-atomic sections of code based on existing critical sections and describe a log-based implementation that can be used to recover a consistent state after a failure. We discuss several subtle semantic issues and implementation tradeoffs. We confirm the ability to rapidly flush caches as a core implementation bottleneck and suggest partial solutions. Experimental results confirm the practicality of our approach and provide insight into the overheads of such a system.

13 pages

Additional Publication Information: A more recent version of this work appears in "Proceedings of the 2014 ACM International Conference on Object Oriented Programming Systems Languages & Applications (OOPSLA)". Here's the DOI link: https://dl.acm.org/citation.cfm?doid=2660193.2660224

  • External Posting Date: February 21, 2014 [Fulltext]. Approved for External Publication
  • Internal Posting Date: February 21, 2014 [Fulltext]

Back to Listing