Electrical Engineering
      and Computer Sciences

Electrical Engineering and Computer Sciences

COLLEGE OF ENGINEERING

UC Berkeley

Read-only Sharing in Operating Systems

Ramesh Govindan

EECS Department
University of California, Berkeley
Technical Report No. UCB/CSD-89-539
November 1989

http://www.eecs.berkeley.edu/Pubs/TechRpts/1989/CSD-89-539.pdf

Sharing read-only code and data between address spaces reduces physical memory usage as well as paging I/O and disk space. In this paper, we study mechanisms for read-only sharing in operating systems. Our work consists of three parts. First, we discuss the issues that arise in the design and implementation of such mechanisms. We examine the solutions adopted by different operating systems. Second, we analyze memory and disk space savings obtained by sharing programs in 4.3 BSD Unix. We show that introduction of a more general sharing mechanism in 4.3 BSD has potential for substantial savings. Finally, we analyze the efficiency of different sharing mechanisms. The read-only sharing mechanism in DASH is shown to be as efficient as the Unix mechanism for program code sharing. Moreover, the DASH approach allows for general read-only sharing (such as shared libraries), not just program code.


BibTeX citation:

@techreport{Govindan:CSD-89-539,
    Author = {Govindan, Ramesh},
    Title = {Read-only Sharing in Operating Systems},
    Institution = {EECS Department, University of California, Berkeley},
    Year = {1989},
    Month = {Nov},
    URL = {http://www.eecs.berkeley.edu/Pubs/TechRpts/1989/5744.html},
    Number = {UCB/CSD-89-539},
    Abstract = {Sharing read-only code and data between address spaces reduces physical memory usage as well as paging I/O and disk space. In this paper, we study mechanisms for read-only sharing in operating systems. Our work consists of three parts. First, we discuss the issues that arise in the design and implementation of such mechanisms. We examine the solutions adopted by different operating systems. Second, we analyze memory and disk space savings obtained by sharing programs in 4.3 BSD Unix. We show that introduction of a more general sharing mechanism in 4.3 BSD has potential for substantial savings. Finally, we analyze the efficiency of different sharing mechanisms. The read-only sharing mechanism in DASH is shown to be as efficient as the Unix mechanism for program code sharing. Moreover, the DASH approach allows for general read-only sharing (such as shared libraries), not just program code.}
}

EndNote citation:

%0 Report
%A Govindan, Ramesh
%T Read-only Sharing in Operating Systems
%I EECS Department, University of California, Berkeley
%D 1989
%@ UCB/CSD-89-539
%U http://www.eecs.berkeley.edu/Pubs/TechRpts/1989/5744.html
%F Govindan:CSD-89-539