Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Charles S. Kline

dblp:78/6248 · DBLP profile ↗
← Back
4ranked-venue papers
0as first author
0since 2021 · last 1983
0000-0001-7939-4898ORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 4

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
4 papers
Distributed systems · 74% Storage systems · 11% Hardware reliability and fault tolerance · 9%
Software engineering, system software, and programming languages
1 paper
Operating systems · 100%

Topics — the 12 heaviest of 13, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Distributed systems
replication
0.031983
Detection of Mutual Inconsistency in Distributed Systems · IEEE Trans. Software Eng. 1983
The LOCUS Distributed Operating System · SOSP 1983
LOCUS - A Network Transparent, High Reliability Distributed System · SOSP 1981
Distributed systems › distributed system architecture
distributed operating systems
0.021983
The LOCUS Distributed Operating System · SOSP 1983
LOCUS - A Network Transparent, High Reliability Distributed System · SOSP 1981
Storage systems › file systems
distributed file system
0.021983
The LOCUS Distributed Operating System · SOSP 1983
LOCUS - A Network Transparent, High Reliability Distributed System · SOSP 1981
Distributed systems
distributed coordination
0.011983
Detection of Mutual Inconsistency in Distributed Systems · IEEE Trans. Software Eng. 1983
Distributed systems
fault tolerance
0.011983
Detection of Mutual Inconsistency in Distributed Systems · IEEE Trans. Software Eng. 1983
Distributed systems › fault tolerance › fault detection and diagnosis
inconsistency detection
0.011983
Detection of Mutual Inconsistency in Distributed Systems · IEEE Trans. Software Eng. 1983
Hardware reliability and fault tolerance › network fault tolerance
network partition tolerance
0.011983
Detection of Mutual Inconsistency in Distributed Systems · IEEE Trans. Software Eng. 1983
Processor architecture and microarchitecture
instruction set architecture
0.011975
The PDP-11 Virtual Machine Architecture: A Case Study · SOSP 1975
Cloud and datacenter computing
virtualization
0.011975
The PDP-11 Virtual Machine Architecture: A Case Study · SOSP 1975
Distributed systems › distributed database
distributed transactions
0.011983
The LOCUS Distributed Operating System · SOSP 1983
Distributed systems › transaction processing
nested transactions
0.011983
The LOCUS Distributed Operating System · SOSP 1983
Operating systems › virtualization
hypervisor
0.011975
The PDP-11 Virtual Machine Architecture: A Case Study · SOSP 1975

Methods — techniques the papers use, named apart from their topics

version vectors · 0.0origin points · 0.0atomic file operations · 0.0
YearPublicationVenuePosition
1983 The LOCUS Distributed Operating System
abstract
LOCUS is a distributed operating system which supports transparent access to data through a network wide filesystem, permits automatic replication of storage, supports transparent distributed process execution, supplies a number of high reliability functions such as nested transactions, and is upward compatible with Unix. Partitioned operation of subnet's and their dynamic merge is also supported.
Bruce J. Walker, Gerald J. Popek, Robert English, Charles S. Kline, Greg Thiel
SOSP4
1983 Detection of Mutual Inconsistency in Distributed Systems
abstract
Many distributed systems are now being developed to provide users with convenient access to data via some kind of communications network. In many cases it is desirable to keep the system functioning even when it is partitioned by network failures. A serious problem in this context is how one can support redundant copies of resources such as files (for the sake of reliability) while simultaneously monitoring their mutual consistency (the equality of multiple copies). This is difficult since network faiures can lead to inconsistency, and disrupt attempts at maintaining consistency. In fact, even the detection of inconsistent copies is a nontrivial problem. Naive methods either 1) compare the multiple copies entirely or 2) perform simple tests which will diagnose some consistent copies as inconsistent. Here a new approach, involving version vectors and origin points, is presented and shown to detect single file, multiple copy mutual inconsistency effectively. The approach has been used in the design of LOCUS, a local network operating system at UCLA.
Douglas Stott Parker Jr., Gerald J. Popek, Gerard Rudisin, Alley Stoughton, Bruce J. Walker, Evelyn Walton, Johanna M. Chow, David A. Edwards, Stephen Kiser, Charles S. Kline
IEEE Trans. Software Eng.10
1981 LOCUS - A Network Transparent, High Reliability Distributed System
abstract
LOCUS is a distributed operating system that provides a very high degree of network transparency while at the same time supporting high performance and automatic replication of storage. By network transparency we mean that at the system call interface there is no need to mention anything network related. Knowledge of the network and code to interact with foreign sites is below this interface and is thus hidden from both users and programs under normal conditions. LOCUS is application code compatible with Unix2, and performance compares favorably with standard, single system Unix. LOCUS runs on a high bandwidth, low delay local network. It is designed to permit both a significant degree of local autonomy for each site in the network while still providing a network-wide, location independent name structure. Atomic file operations and extensive synchronization are supported.
Gerald J. Popek, Bruce J. Walker, Johanna M. Chow, David A. Edwards, Charles S. Kline, Gerard Rudisin, Greg Thiel
SOSP5
1975 The PDP-11 Virtual Machine Architecture: A Case Study
Gerald J. Popek, Charles S. Kline
SOSP2