Recovery using virtual memory

Kolodner, Elliot K.

doi:10.1016/0167-4048(88)90254-4

Cited by 6 publications

(2 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It requires several features that Unix does not provide, such as the ability to UpinN pages to prevent them from being written to disk. This design is discussed in [11].…”

Section: R E C O V E R Ymentioning

confidence: 99%

Implementation of Argus

Liskov

Curtis

Johnson

et al. 1987

Proceedings of the Eleventh ACM Symposium on Operating Systems Principles - SOSP '87

View full text Add to dashboard Cite

Argus is a programming language and system developed to support the construction and execution of distributed programs. This paper describes the implementation of Argus, with particular emphasis on the way we implement atomic actions, because this is where Argus differs most from other implemented systems. The paper also discusses the performance of Argus. The cost of actions is quite reasonable, indicating that action systems like Argus are practical.

show abstract

“…It requires several features that Unix does not provide, such as the ability to UpinN pages to prevent them from being written to disk. This design is discussed in [11].…”

Section: R E C O V E R Ymentioning

confidence: 99%

Implementation of Argus

Liskov

Curtis

Johnson

et al. 1987

Proceedings of the Eleventh ACM Symposium on Operating Systems Principles - SOSP '87

View full text Add to dashboard Cite

show abstract

“…Realize however, that most of the data in virtual memory will actually be intact on a disk (in swap space) after a crash. Work is currently underway on how to recover virtual memory following crashes [16]. The problem of very large virtual memories still exists.…”

Section: Large Amounts Of Datamentioning

confidence: 99%

Issues in the design of object-oriented database programming languages

Bloom¹,

Zdonik

1987

SIGPLAN Not.

View full text Add to dashboard Cite

We see a trend toward extending object-oriented languages in the direction of databases, and, at the same time, toward extending database systems with object-oriented ideas. On the surface, these two activities seem to be moving in a consistent direction. However, at a deeper level, we see difficulties that may inhibit their ending up at the same point. We feel that many of these difficufties are a result of the underlying assumptions that are inherent in the fields of programming language and database systems research. Many of these assumptions are historical and contribute to a set of cultural biases that often prevent the two communities from interacting as effectively as possible.

show abstract