A modular computer sharing systems
Communications of the ACM
The external access network of a modular computer system
AFIPS '72 (Spring) Proceedings of the May 16-18, 1972, spring joint computer conference
Modularity and multi-microprocessor structures
MICRO 7 Conference record of the 7th annual workshop on Microprogramming
Experiences with Performance Measurement and Modeling of a Processor Array
IEEE Transactions on Computers
A Reliability Model for Gracefully Degrading and Standby-Sparing Systems
IEEE Transactions on Computers
Multiprocessor Scheduling with Memory Allocation A Deterministic Approach
IEEE Transactions on Computers
On Evaluating the Performability of Degradable Computing Systems
IEEE Transactions on Computers
The external access network of a modular computer system
AFIPS '72 (Spring) Proceedings of the May 16-18, 1972, spring joint computer conference
Dynamic confirmation of system integrity
AFIPS '72 (Fall, part I) Proceedings of the December 5-7, 1972, fall joint computer conference, part I
An overview of fault-tolerant digital system architecture
AFIPS '77 Proceedings of the June 13-16, 1977, national computer conference
Research in data security: policies and projects
AFIPS '74 Proceedings of the May 6-10, 1974, national computer conference and exposition
| Hi-index | 0.01 |
The architecture of most interactive systems is based on the general strategy that suitable terminal service can be provided by a central processor that is timemultiplexed among all the active terminals. In order to achieve adequate response time in an interactive environment, the CPU is usually time sliced. Other major system facilities such as I/O channels and secondary storage units are also shared among the users, and multiprogramming techniques are employed to keep all the major system resources as fully utilized as possible. An operating system is usually developed which performs these functions as well as supervising the terminal communications, implementing a system-wide filing subsystem, handling user commands, etc. The result of combining these and other functions into a time-sharing operating system is a highly complex software system which transforms what is basically a batch processing computer structure into a multi-terminal system with significant limitations that are an outgrowth of this strategy. While a failure can occur in any section of the hardware or software, we know that hardware failures are more likely to occur in the electromechanical and core memory sectors than in solid state logic, and that software failures tend to be concentrated in the more complex areas of code. Failures of hardware components may require modification of the operating system in order to regain operational status since the allocation strategies may need more than parametric modification when system resources are affected.