@article{
 title = {The Expected Lifetime of Single-Address-Space Operating Systems},
 type = {article},
 year = {1996},
 keywords = {dartmouth-cs,distributed-computing,operating-system},
 pages = {155-178},
 volume = {9},
 websites = {http://www.cs.dartmouth.edu/~dfk/papers/kotz-jaddrtrace.pdf},
 publisher = {MIT Press},
 id = {ce14d4ee-2680-3c3e-b502-ecddce328d6b},
 created = {2018-07-12T21:32:20.067Z},
 file_attached = {false},
 profile_id = {f954d000-ce94-3da6-bd26-b983145a920f},
 group_id = {b0b145a3-980e-3ad7-a16f-c93918c606ed},
 last_modified = {2018-07-12T21:32:20.067Z},
 read = {false},
 starred = {false},
 authored = {false},
 confirmed = {true},
 hidden = {false},
 citation_key = {kotz:jaddrtrace},
 source_type = {article},
 private_publication = {false},
 abstract = {Trends toward shared-memory programming paradigms, large (64-bit) address spaces, and memory-mapped files have led some to propose the use of a single virtual-address space, shared by all processes and processors. To simplify address-space management, some have claimed that a 64-bit address space is sufficiently large that there is no need to ever re-use addresses. Unfortunately, there has been no data to either support or refute these claims, or to aid in the design of appropriate address-space management policies. In this paper, we present the results of extensive kernel-level tracing of the workstations on our campus, and discuss the implications for single-address-space operating systems. We found that single-address-space systems will probably not outgrow the available address space, but only if reasonable space-allocation policies are used, and only if the system can adapt as larger address spaces become available.},
 bibtype = {article},
 author = {Kotz, David and Crow, Preston},
 journal = {Computing Systems},
 number = {3}
}

{"_id":"J5N9EmaZ8x3DXEmNA","bibbaseid":"kotz-crow-theexpectedlifetimeofsingleaddressspaceoperatingsystems-1996","downloads":0,"creationDate":"2019-02-15T15:15:01.332Z","title":"The Expected Lifetime of Single-Address-Space Operating Systems","author_short":["Kotz, D.","Crow, P."],"year":1996,"bibtype":"article","biburl":null,"bibdata":{"title":"The Expected Lifetime of Single-Address-Space Operating Systems","type":"article","year":"1996","keywords":"dartmouth-cs,distributed-computing,operating-system","pages":"155-178","volume":"9","websites":"http://www.cs.dartmouth.edu/~dfk/papers/kotz-jaddrtrace.pdf","publisher":"MIT Press","id":"ce14d4ee-2680-3c3e-b502-ecddce328d6b","created":"2018-07-12T21:32:20.067Z","file_attached":false,"profile_id":"f954d000-ce94-3da6-bd26-b983145a920f","group_id":"b0b145a3-980e-3ad7-a16f-c93918c606ed","last_modified":"2018-07-12T21:32:20.067Z","read":false,"starred":false,"authored":false,"confirmed":"true","hidden":false,"citation_key":"kotz:jaddrtrace","source_type":"article","private_publication":false,"abstract":"Trends toward shared-memory programming paradigms, large (64-bit) address spaces, and memory-mapped files have led some to propose the use of a single virtual-address space, shared by all processes and processors. To simplify address-space management, some have claimed that a 64-bit address space is sufficiently large that there is no need to ever re-use addresses. Unfortunately, there has been no data to either support or refute these claims, or to aid in the design of appropriate address-space management policies. In this paper, we present the results of extensive kernel-level tracing of the workstations on our campus, and discuss the implications for single-address-space operating systems. We found that single-address-space systems will probably not outgrow the available address space, but only if reasonable space-allocation policies are used, and only if the system can adapt as larger address spaces become available.","bibtype":"article","author":"Kotz, David and Crow, Preston","journal":"Computing Systems","number":"3","bibtex":"@article{\n title = {The Expected Lifetime of Single-Address-Space Operating Systems},\n type = {article},\n year = {1996},\n keywords = {dartmouth-cs,distributed-computing,operating-system},\n pages = {155-178},\n volume = {9},\n websites = {http://www.cs.dartmouth.edu/~dfk/papers/kotz-jaddrtrace.pdf},\n publisher = {MIT Press},\n id = {ce14d4ee-2680-3c3e-b502-ecddce328d6b},\n created = {2018-07-12T21:32:20.067Z},\n file_attached = {false},\n profile_id = {f954d000-ce94-3da6-bd26-b983145a920f},\n group_id = {b0b145a3-980e-3ad7-a16f-c93918c606ed},\n last_modified = {2018-07-12T21:32:20.067Z},\n read = {false},\n starred = {false},\n authored = {false},\n confirmed = {true},\n hidden = {false},\n citation_key = {kotz:jaddrtrace},\n source_type = {article},\n private_publication = {false},\n abstract = {Trends toward shared-memory programming paradigms, large (64-bit) address spaces, and memory-mapped files have led some to propose the use of a single virtual-address space, shared by all processes and processors. To simplify address-space management, some have claimed that a 64-bit address space is sufficiently large that there is no need to ever re-use addresses. Unfortunately, there has been no data to either support or refute these claims, or to aid in the design of appropriate address-space management policies. In this paper, we present the results of extensive kernel-level tracing of the workstations on our campus, and discuss the implications for single-address-space operating systems. We found that single-address-space systems will probably not outgrow the available address space, but only if reasonable space-allocation policies are used, and only if the system can adapt as larger address spaces become available.},\n bibtype = {article},\n author = {Kotz, David and Crow, Preston},\n journal = {Computing Systems},\n number = {3}\n}","author_short":["Kotz, D.","Crow, P."],"urls":{"Website":"http://www.cs.dartmouth.edu/~dfk/papers/kotz-jaddrtrace.pdf"},"bibbaseid":"kotz-crow-theexpectedlifetimeofsingleaddressspaceoperatingsystems-1996","role":"author","keyword":["dartmouth-cs","distributed-computing","operating-system"],"downloads":0},"search_terms":["expected","lifetime","single","address","space","operating","systems","kotz","crow"],"keywords":["dartmouth-cs","distributed-computing","operating-system","distributed computing","operating system"],"authorIDs":[]}