Grasshopper: an orthogonally persistent operating system
Computing Systems
EROS: a fast capability system
Proceedings of the seventeenth ACM symposium on Operating systems principles
User-level checkpointing through exportable kernel state
IWOOOS '96 Proceedings of the 5th International Workshop on Object Orientation in Operating Systems (IWOOOS '96)
Programming Languages For Interactive Computing
Electronic Notes in Theoretical Computer Science (ENTCS)
Persistent systems techniques in forensic acquisition of memory
Digital Investigation: The International Journal of Digital Forensics & Incident Response
| Hi-index | 0.00 |
An operating system is persistent if all objects it supports have a lifetime independent of the context in which they were created. This concept, known as orthogonal persistence, extends to data objects and computations (processes and threads). A persistent computation is required to survive system crashes and shutdowns. After the service is restored it is expected to continue with a very small loss of productive activity. Over its lifetime every computation interacts with some transient aspects of its environment, for example I/O devices, network connections etc. The main issue in providing support for persistent computations is how to control such interactions in order to prevent them from becoming a part of the preserved state of a computation. These interactions are mediated by the system kernel; therefore the provision of persistent computations relates directly to the persistence of the kernel itself. In this paper we examine the solutions offered by persistent operating systems constructed to date, and we propose a new approach, implemented in the Grasshopper operating system. We show that this approach is sufficiently flexible to handle all problems identified so far, and sufficiently general to suit any operating system.