ACM Letters on Programming Languages and Systems · 1992 · 30 citations · 17 references
EngineeringComputer EngineeringComputer ScienceComputer ArchitectureMemoryStorage SystemsGarbage CollectionMemory HierarchyMemory Hierarchy DesignMemory ManagementMemory Subsystem DesignGarbage Collection OverheadHeap ManagementHeap OrganizationMemory Management UnitsObject MemoryPagingReal-time Garbage CollectionSystem Configuration
Modern object-oriented languages and programming paradigms require finer-grain division of memory than is provided by traditional paging and segmentation systems. This paper describes the design of an OSM (Object Space Manager) that allows partitioning of real memory on object, rather than page, boundaries. The time required by the OSM to create an object, or to find the beginning of an object given a pointer to any location within it, is approximately one memory cycle. Object sizes are limited only by the availability of address bits. In typical configurations of object-oriented memory modules, one OSM chip is required for every 16 RAM chips. The OSM serves a central role in the implementation of a hardware-assisted garbage collection system in which the worst-case stop-and-wait garbage collection delay ranges between 10 and 500 μsec, depending on the system configuration.
17
List processing in real time on a serial computer
Henry G. Baker · Communications of the ACM · 1978 · 592 citations · Full text
David Ungar · ACM SIGSOFT Software Engineering Notes · 1984 · 487 citations
Real-time concurrent collection on stock multiprocessors
Andrew W. Appel · ACM SIGPLAN Notices · 2004 · 216 citations
Mostly parallel garbage collection
Hans‐J. Boehm, Alan Demers, Scott Shenker · 1991 · 206 citations · Full text