Non-volatile main memory, such as memristors or phase change memory, can revolutionize the way programs persist data. In-memory objects can themselves be persistent without the need for a separate persistent 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 our system, called Atlas, which adds 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.
Thu 23 Oct
|13:30 - 13:52|
|Link to publication|
|13:52 - 14:15|
Guy L. Steele Jr.Oracle Labs, Doug LeaState University of New York (SUNY) Oswego, Christine H. FloodRed HatLink to publication
|14:15 - 14:37|
Malavika SamakIndian Institute of Science, Bangalore, Murali Krishna RamanathanIndian Institute of Science, BangaloreLink to publication
|14:37 - 15:00|
Tom BerganUniversity of Washington, Dan GrossmanUniversity of Washington, Luis CezeUniversity of WashingtonLink to publication