Single Address Space Operating Systems Software
Single Address Space Operating Systems Software
Single Address Space
Single Address Space Operating Systems (SASOSs) are OSs in which all code and data exists within one, big, shared address space, often threaded. Using one address space facilitates and enhances sharing and cooperation, because it lets addresses have a unique (for all time) representation or interpretation. Thus, pointer-based data structures can be directly communicated and shared between programs at any time, and can be stored directly on secondary storage with no need to translate. Such structures are simplified by using larger address spaces.
Some SASOS benefits: 1) Can be made as secure as traditional systems. 2) Are not inherently less efficient than traditional systems. 3) Improve performance over traditional systems on some types of important applications. 4) Give a dual cost advantage: lower initial cost, lower incremental cost.
Top: Computers: Software: Operating Systems: Single Address Space
See Also:
- Part of Computer Science Bibliography Collection of Alf-Christian Achilles.
- Where stale pointers make it hard to re-use addresses, some have claimed that a 64-bit address space is so big that there is no need to ever re-use addresses. Results of extensive kernel-level tracing of department workstations.
- Orthogonally persistent, research SASOS. Persistence gives a fundamentally different model of computing from that supported by normal OSs, so using such for persistence research is inappropriate.
- Orthogonally persistent, capability-based secure SASOS using L4 2nd generation microkernel. Goals: Prove SASOSs can run on normal hardware, be as secure as normal OSs; can be as efficient as, and are faster than, normal OSs in some important uses; can be
- One of many reports available on a list of publications from Grasshopper OS. Scroll down to mid-page. Explains rationale and design approach for SASOSs. Abstracts, FTP downloads in formats: PDF, PS, PS.GZ.
- Multitasking SASOS with transparent data persistence: users and application programmers need not know or care that system memory is transient and must be written to disk to persist across reboots, all details done by OS, so once data is made, it exists un
- Exploring a new OS structure, tuned to the needs of complex applications (eg, CAD/CAM) where a number of cooperating programs manipulate a large shared persistent database of objects.
- Short, annotated, alphabetically sorted list and links, part of larger system.
- From Proceedings of the International Conference on Architectural Support for Programming Languages and Operating Systems, Boston, USA, October 1992.
- Mail lists, projects, biographies (BibTeX, HTML long, HTML sans abstracts), a few links to other SASOS sites.
- SASOS research, and the Sombrero OS, at Arizona State University.
Newsgroups:
| | | | | | |
Copyright © 1995-2007 Internet Advertising Solutions, Inc.
Copyright Notice | Privacy Policy | Site Map | APR
|
 |
|
