Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109262
J. Banâtre, M. Banâtre, Gilles Muller
A fault-tolerant multiprocessor architecture that is based on standard processors associated with stable storage boards is presented. The hardware architecture of the stable storage board and its software interface are briefly described. The hardware organization of the fault-tolerant multiprocessor is detailed, and some functionalities of a secure kernel are examined. The current status of the project is indicated.<>
{"title":"Architecture of fault-tolerant multiprocessor workstations","authors":"J. Banâtre, M. Banâtre, Gilles Muller","doi":"10.1109/WWOS.1989.109262","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109262","url":null,"abstract":"A fault-tolerant multiprocessor architecture that is based on standard processors associated with stable storage boards is presented. The hardware architecture of the stable storage board and its software interface are briefly described. The hardware organization of the fault-tolerant multiprocessor is detailed, and some functionalities of a secure kernel are examined. The current status of the project is indicated.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"238 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116171581","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109260
M. S. Atkins
A distributed data structure called a MOOSE (modifiable object structure), which is both efficient enough and general enough to be used by a wide variety of parallel algorithms, is outlined. The MOOSE structure is aimed at a loosely coupled distributed system in which several processors are connected over a local area network. It is implemented in the high-level distributed programming language SR on several Sun-2 and Sun-3 workstations running the Unix operating system and connected by an Ethernet. The MOOSE shared memory has been designed with customizable features for efficiency of implementation in such an environment. This enables the communication and computation performance of parallel algorithms on non-shared-memory hardware to be studied. If the application is run in the background on several network nodes, automatic load balancing is achieved and the programs may be tolerant of node failure during the computation.<>
{"title":"Efficient shared memory for testing parallel algorithms on distributed systems","authors":"M. S. Atkins","doi":"10.1109/WWOS.1989.109260","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109260","url":null,"abstract":"A distributed data structure called a MOOSE (modifiable object structure), which is both efficient enough and general enough to be used by a wide variety of parallel algorithms, is outlined. The MOOSE structure is aimed at a loosely coupled distributed system in which several processors are connected over a local area network. It is implemented in the high-level distributed programming language SR on several Sun-2 and Sun-3 workstations running the Unix operating system and connected by an Ethernet. The MOOSE shared memory has been designed with customizable features for efficiency of implementation in such an environment. This enables the communication and computation performance of parallel algorithms on non-shared-memory hardware to be studied. If the application is run in the background on several network nodes, automatic load balancing is achieved and the programs may be tolerant of node failure during the computation.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125949276","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109264
N. Faller, P. Salenbauch
A description is given of PLURIX, a Unix-like operating system designed to control PEGASUS-32X, a symmetric multiprocessor supermicro based on several Motorola 68020 microprocessor. The differences and similarities between PLURIX and Unix are examined. The multiprocessing capabilities of PLURIX in the PEGASUS-32X environment are discussed, covering the hardware environment, multiprocessing objectives, mutual exclusion primitives, and event primitives.<>
{"title":"PLURIX: a multiprocessing Unix-like operating system","authors":"N. Faller, P. Salenbauch","doi":"10.1109/WWOS.1989.109264","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109264","url":null,"abstract":"A description is given of PLURIX, a Unix-like operating system designed to control PEGASUS-32X, a symmetric multiprocessor supermicro based on several Motorola 68020 microprocessor. The differences and similarities between PLURIX and Unix are examined. The multiprocessing capabilities of PLURIX in the PEGASUS-32X environment are discussed, covering the hardware environment, multiprocessing objectives, mutual exclusion primitives, and event primitives.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"43 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114520586","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109270
W. Leung, L. F. Morgan, M. J. Morgan, B. Wong
Some software mechanisms implemented in the multimedia workstations of an experimental multimedia teleconferencing system are discussed. These mechanisms are used to interface with the different types of devices involved in multimedia conference applications and to direct information flow among them. They are concerned with teleconferencing applications with which people in different offices can talk to each other while simultaneously editing the same file, debugging the same program, or working on some other arbitrary applications. Users engaged in teleconferencing may use multimedia workstations equipped with peripherals such as telephone handsets, image scanners, network interfaces, and mass storage. In the prototype system, the workstations are connected to an experimental fast packet switch capable of switching voice, data, and video on a single network.<>
{"title":"The connector and active devices mechanisms for constructing multimedia applications","authors":"W. Leung, L. F. Morgan, M. J. Morgan, B. Wong","doi":"10.1109/WWOS.1989.109270","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109270","url":null,"abstract":"Some software mechanisms implemented in the multimedia workstations of an experimental multimedia teleconferencing system are discussed. These mechanisms are used to interface with the different types of devices involved in multimedia conference applications and to direct information flow among them. They are concerned with teleconferencing applications with which people in different offices can talk to each other while simultaneously editing the same file, debugging the same program, or working on some other arbitrary applications. Users engaged in teleconferencing may use multimedia workstations equipped with peripherals such as telephone handsets, image scanners, network interfaces, and mass storage. In the prototype system, the workstations are connected to an experimental fast packet switch capable of switching voice, data, and video on a single network.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116839893","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109273
G. Neufeld, S. Chanson
An overview is given of a distributed object-oriented operating system project called the Raven project. The Raven operating system is intended for use in a variety of applications, such as office systems and control systems. It is intended to work as a high-speed, fault-tolerant system. Raven includes both a programming language and an operating system. Raven is object-oriented in that it supports multiple inherited types. It is fault tolerant in that it supports persistent objects, recoverable objects, and atomic transactions. The major emphasis of the work is the overall design of the language and system, distributed configuration management, distributed single-level object store, RAM-based high-speed transaction management, and object-based parallel communication. All of these areas of work are being developed within the context of autonomous administration domains.<>
{"title":"The Raven project (distributed object-oriented OS)","authors":"G. Neufeld, S. Chanson","doi":"10.1109/WWOS.1989.109273","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109273","url":null,"abstract":"An overview is given of a distributed object-oriented operating system project called the Raven project. The Raven operating system is intended for use in a variety of applications, such as office systems and control systems. It is intended to work as a high-speed, fault-tolerant system. Raven includes both a programming language and an operating system. Raven is object-oriented in that it supports multiple inherited types. It is fault tolerant in that it supports persistent objects, recoverable objects, and atomic transactions. The major emphasis of the work is the overall design of the language and system, distributed configuration management, distributed single-level object store, RAM-based high-speed transaction management, and object-based parallel communication. All of these areas of work are being developed within the context of autonomous administration domains.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127823760","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109282
B. Welch, Mary Baker, F. Douglis, J. Hartman, M. Rosenblum, J. Ousterhout
The authors advocate keeping state in main memory instead of logging state to disk, so that higher performance services can be implemented. They are motivated by their distributed file system which uses stateful servers to support a high-performance distributed caching system. For reliability, a server's state is replicated in the main memory of other hosts so that the system can recover from the failure of a server. After a server reboots, its clients help it rebuild its internal state. The authors point out that as networks and processors get faster, but disks do not, relying on other hosts will be more efficient than using disks.<>
{"title":"Sprite position statement: use distributed state for failure recovery","authors":"B. Welch, Mary Baker, F. Douglis, J. Hartman, M. Rosenblum, J. Ousterhout","doi":"10.1109/WWOS.1989.109282","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109282","url":null,"abstract":"The authors advocate keeping state in main memory instead of logging state to disk, so that higher performance services can be implemented. They are motivated by their distributed file system which uses stateful servers to support a high-performance distributed caching system. For reliability, a server's state is replicated in the main memory of other hosts so that the system can recover from the failure of a server. After a server reboots, its clients help it rebuild its internal state. The authors point out that as networks and processors get faster, but disks do not, relying on other hosts will be more efficient than using disks.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114194574","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109269
M. Kazar
While replication of administrative databases is important, quite often lazy propagation of updates does not suffice. This argument is couched in terms of experience with the Andrew file system (AFS) but the author believes that it generalizes to many environments. He discusses in some detail a replication library his group built, on top of which they built all of the AFS administrative servers. This library, named Ubik, is interesting for three reasons. First, it has a very simple programming interface, making it relatively easy to understand. Second, the library is quite easy to implement, while still being useful for a large class of server applications. Finally, the library uses an interesting nonblocking (in the database sense) commit protocol, providing good write as well as read availability. The author outlines Ubik's goals, gives an overview of it, and describes its quorum completion algorithm in some detail.<>
{"title":"Ubik: replicated servers made easy","authors":"M. Kazar","doi":"10.1109/WWOS.1989.109269","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109269","url":null,"abstract":"While replication of administrative databases is important, quite often lazy propagation of updates does not suffice. This argument is couched in terms of experience with the Andrew file system (AFS) but the author believes that it generalizes to many environments. He discusses in some detail a replication library his group built, on top of which they built all of the AFS administrative servers. This library, named Ubik, is interesting for three reasons. First, it has a very simple programming interface, making it relatively easy to understand. Second, the library is quite easy to implement, while still being useful for a large class of server applications. Finally, the library uses an interesting nonblocking (in the database sense) commit protocol, providing good write as well as read availability. The author outlines Ubik's goals, gives an overview of it, and describes its quorum completion algorithm in some detail.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115124964","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109280
B. Schatz
An information environment wherein a wide variety of network data is modeled as a single logical information space is now possible via a workstation network. Its effective implementation has potentially significant implications for workstation operating systems. The author discusses information environments in general, user interaction with information spaces, a substantial research prototype, operating system issues associated with its implementation, and future environments.<>
{"title":"A prototype information environment","authors":"B. Schatz","doi":"10.1109/WWOS.1989.109280","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109280","url":null,"abstract":"An information environment wherein a wide variety of network data is modeled as a single logical information space is now possible via a workstation network. Its effective implementation has potentially significant implications for workstation operating systems. The author discusses information environments in general, user interaction with information spaces, a substantial research prototype, operating system issues associated with its implementation, and future environments.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133340297","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109272
J. Mogul
It is argued that although the stateless server model has proved quite useful to network file systems, statelessness is a means to an end and should not be an end in itself. The author maintains that statelessness can be a severe impediment to building efficient, reliable systems. He concludes that if its actual advantages can be preserved in a stateful system without too much effort, statelessness as a dogma should be discarded.<>
{"title":"What is the right amount of statelessness in a file server?","authors":"J. Mogul","doi":"10.1109/WWOS.1989.109272","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109272","url":null,"abstract":"It is argued that although the stateless server model has proved quite useful to network file systems, statelessness is a means to an end and should not be an end in itself. The author maintains that statelessness can be a severe impediment to building efficient, reliable systems. He concludes that if its actual advantages can be preserved in a stateful system without too much effort, statelessness as a dogma should be discarded.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"31 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125514010","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109265
P. Guedes, J. Marques
An overview is given of the Comandos project of the European Strategic Programme for Research on Information Technology (ESPRIT). The initial phase of the project was devoted to the definition of the Comandos virtual machine and resulted from contributions of the different partners in the project. Then several testbed implementations were started to validate the basic ideas of the architecture. The virtual machine and its supporting architecture are described. Some design issues faced in the development of the prototype are presented, with particular reference to the object memory. The current status of the project and future plans are briefly discussed.<>
{"title":"Operating system support for an object-oriented environment","authors":"P. Guedes, J. Marques","doi":"10.1109/WWOS.1989.109265","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109265","url":null,"abstract":"An overview is given of the Comandos project of the European Strategic Programme for Research on Information Technology (ESPRIT). The initial phase of the project was devoted to the definition of the Comandos virtual machine and resulted from contributions of the different partners in the project. Then several testbed implementations were started to validate the basic ideas of the architecture. The virtual machine and its supporting architecture are described. Some design issues faced in the development of the prototype are presented, with particular reference to the object memory. The current status of the project and future plans are briefly discussed.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"84 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121070508","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：