5 citations found. Retrieving documents...
Alan Dearle and David Hulse. Operating system support for persistent systems: Past, present, future. Software - Practice and Experience, 30(4):295--324, 2000.

 Home/Search   Document Details and Download   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Managing Kernel Memory Resources from User Level - Haeberlen (2003)   (Correct)

....runs with user privileges, it logically owns part of kernel memory and can access this part directly using mappings in its address space. The checkpoint server is also allowed to revoke certain privileges from the kernel, e.g. to implement copy on write for kernel metadata. The Charm microkernel [12], which is derived from the Grasshopper system [11] exposes its metadata to user level in order to support applications in implementing their own persistence policy. However, applications are not allowed to create or modify metadata; security related metadata is not exposed. 2.3 Summary In ....

Alan Dearle and David Hulse. Operating system support for persistent systems: Past, present, future. Software - Practice and Experience, 30(4):295--324, 2000.


Termination and Rollback in Language-Based Systems - Rudys (2002)   (Correct)

....propagate changes. Finally, Howell [47] describes an implementation of Java persistence which operates above the operating system but below the language run time system. A more complete discussion of operating system support for persistence and transactional systems is provided by Dearle and Hulse [27]. 47 The operating system can also be used to enforce language security invariants. For language security, the operating system already has built in protections for cross domain access of state. However, the operating system uses processes to separate protection domains, so individual codelets ....

A. Dearle and D. Hulse. Operating system support for persistent systems: Past, present and future. Software: Practice and Experience Special Issue: Persistent Object Systems, 30(4):295--324, 2000.


Implementation of an Orthogonally Persistent L4 µ-Kernel Based.. - Ceelen   (Correct)

....because it is not based upon a kernel and uses abstractions specially designed with persistence in mind. These kernel abstractions are used to implement persistence on kernel level. Based on the experience with Grasshopper its designers later created a kernel based operating system, Charm [17], to support persistent applications. In Charm, the kernel provides the application system with mechanisms to implement its own persistence policy by exposing all in kernel meta data to the application. The application has to ensure persistence itself by storing the data. As such, no specific ....

Alan Dearle and David Hulse, Operating system support for persistent systems: past, present, future, Software - Practice and Experience, Special Issue on Persistent Object Systems, 30(4):295-324, 2000.


Transactional Rollback for Language-Based Systems - Rudys, Wallach (2002)   (5 citations)  (Correct)

....[30] to propagate changes. Finally, Howell [19] describes an implementation of Java persistence which operates above the operating system but below the language runtime. A more complete discussion of operating system support for persistence and transactional systems is provided by Dearle and Hulse [11]. The operating system can also be used to enforce language security invariants. For language security, the operating system already has built in protections for crossdomain access of state. However, the operating system uses processes to separate protection domains, so individual codelets have ....

A. Dearle and D. Hulse. Operating system support for persistent systems: Past, present and future. Software: Practice and Experience Special Issue: Persistent Object Systems, 30(4):295--324, 2000.


Transparent Orthogonal Checkpointing Through User-Level.. - Skoglund, Ceelen, Liedtke (2000)   (3 citations)  (Correct)

....based upon kernels. An exception to this rule is Grasshopper [2] Grasshopper hopes to achieve persistence through the use of some specially designed kernel abstractions. Based on the experiences learned from Grasshopper, the designers have later created a kernel based operating system, Charm [3], aiming at supporting persistent applications. With Charm, no particular persistence model is enforced upon the applications. The kernel instead provides the application system with mechanisms to construct their own persistence policy. In short, all in kernel meta data (such as page tables) are ....

Alan Dearle and David Hulse. Operating system support for persistent systems: past, present and future. Software { Practice and Experience, Special Issue on Persistent Object Systems, 30(4):295-324, 2000.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC