The Rio File Cache: Surviving Operating System Crashes (1996)
Cached
Download Links
- [www-cse.ucsd.edu]
- [www.bennetyee.org]
- [www.cs.ucsd.edu]
- [www.eecs.umich.edu]
- [www.eecs.umich.edu]
- [www.eecs.umich.edu]
- [www.eecs.umich.edu]
- [www.cs.toronto.edu]
- DBLP
Other Repositories/Bibliography
| Venue: | In Proc. 7th Intl. Conference on Architectural Support for Programming Languages and Operating Systems (ASPLOS |
| Citations: | 105 - 13 self |
BibTeX
@INPROCEEDINGS{Chen96therio,
author = {Peter M. Chen and Wee Teck Ng and Gurushankar Rajamani and Christopher M. Aycock},
title = {The Rio File Cache: Surviving Operating System Crashes},
booktitle = {In Proc. 7th Intl. Conference on Architectural Support for Programming Languages and Operating Systems (ASPLOS},
year = {1996}
}
Years of Citing Articles
OpenURL
Abstract
Abstract: One of the fundamental limits to high-performance, high-reliability file systems is memory’s vulnerability to system crashes. Because memory is viewed as unsafe, systems periodically write data back to disk. The extra disk traffic lowers performance, and the delay period before data is safe lowers reliability. The goal of the Rio (RAM I/O) file cache is to make ordinary main memory safe for persistent storage by enabling memory to survive operating system crashes. Reliable memory enables a system to achieve the best of both worlds: reliability equivalent to a write-through file cache, where every write is instantly safe, and performance equivalent to a pure write-back cache, with no reliability-induced writes to disk. To achieve reliability, we protect memory during a crash and restore it during a reboot (a “warm ” reboot). Extensive crash tests show that even without protection, warm reboot enables memory to achieve reliability close to that of a write-through file system while performing 20 times faster. Rio makes all writes immediately permanent, yet performs faster than systems that lose 30 seconds of data on a crash: 35% faster than a standard delayed-write file system and 8 % faster than a system that delays both data and metadata. For applications that demand even higher levels of reliability, Rio’s optional protection mechanism makes memory even safer than a write-through file system while while lowering performance 20 % compared to a pure write-back system. 1







