Protection traps and alternatives for memory management of an object-oriented language

Antony L. Hosking*, J. Eliot B. Moss

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

24 Citations (Scopus)

Abstract

Many operating systems allow user programs to specify the protection level (inaccessible, read-only, read-write) of pages in their virtual memory address space, and to handle any protection violations that may occur. Such page-protection techniques have been exploited by several user-level algorithms for applications including generational garbage collection and persistent stores. Unfortunately, modern hardware has made efficient handling of page protection faults more difficult.

Original languageEnglish
Title of host publicationOperating Systems Review (ACM)
Editors Anon
Pages106-119
Number of pages14
Edition5
DOIs
Publication statusPublished - Dec 1993
Externally publishedYes
EventProceedings of the 14th ACM Symposium on Operating Systems Principles - Asheville, NC, USA
Duration: 5 Dec 19938 Dec 1993

Publication series

NameOperating Systems Review (ACM)
Number5
Volume27
ISSN (Print)0163-5980

Conference

ConferenceProceedings of the 14th ACM Symposium on Operating Systems Principles
CityAsheville, NC, USA
Period5/12/938/12/93

Fingerprint

Dive into the research topics of 'Protection traps and alternatives for memory management of an object-oriented language'. Together they form a unique fingerprint.

Cite this