BibTeX: David Kotz papers for project 'sasos'.
For more information, visit this web page:
https://kotz.cs.dartmouth.edu/research/project/sasos/index.html

@InProceedings{kotz:addrtrace,
  author =        {David Kotz and Preston Crow},
  title =         {{The Expected Lifetime of ``Single-Address-Space'' Operating Systems}},
  booktitle =     {{Proceedings of the ACM SIGMETRICS Conference on Measurement and Modeling of Computer Systems}},
  year =          1994,
  month =         {May},
  pages =         {161--170},
  publisher =     {ACM},
  copyright =     {ACM},
  DOI =           {10.1145/183019.183036},
  URL =           {https://kotz.cs.dartmouth.edu/research/kotz-addrtrace/index.html},
  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. Typical proposals require the single address space to contain all process-private data, shared data, and stored files. To simplify management of an address space where stale pointers make it difficult to re-use addresses, 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 in our department, and discuss the implications for single-address-space operating systems. We found that single-address-space systems will 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.},
}

@TechReport{kotz:addrtrace-tr,
  author =        {David Kotz and Preston Crow},
  title =         {{The Expected Lifetime of ``Single-Address-Space'' Operating Systems}},
  institution =   {Dept. of Math and Computer Science, Dartmouth College},
  year =          1993,
  month =         {October},
  number =        {PCS-TR93-198},
  copyright =     {the authors},
  URL =           {https://kotz.cs.dartmouth.edu/research/kotz-addrtrace-tr/index.html},
  note =          {Revised version appeared in SIGMETRICS '94, and revised again on March 15, 1996},
  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.},
}

@Article{kotz:jaddrtrace,
  author =        {David Kotz and Preston Crow},
  title =         {{The Expected Lifetime of Single-Address-Space Operating Systems}},
  journal =       {Computing Systems},
  year =          1996,
  month =         {Summer},
  volume =        9,
  number =        3,
  pages =         {155--178},
  publisher =     {MIT Press},
  copyright =     {USENIX Association},
  URL =           {https://kotz.cs.dartmouth.edu/research/kotz-jaddrtrace/index.html},
  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.},
}