2001
DOI: 10.1007/3-540-45306-7_21
|View full text |Cite
|
Sign up to set email alerts
|

Constant-Time Root Scanning for Deterministic Garbage Collection

Abstract: Abstract. Root scanning is the task of identifying references to heap objects that are stored outside of the heap itself, in global and local variables and on the execution stack. Root scanning is particularly difficult within an incremental garbage collector that needs to be deterministic or give hard realtime guarantees. Here, a method that allows exact root scanning is presented. The basic idea is to ensure that copies of all root references exist on the heap whenever the garbage collector might become acti… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
27
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 24 publications
(27 citation statements)
references
References 21 publications
0
27
0
Order By: Relevance
“…Another good example of incremental root scanning is Siebert's approach [93]. As it is a part of a collector which can provide a certain degree of real-time guarantees, it will be introduced along with the collector in the next section.…”
Section: Incremental Root Scanningmentioning
confidence: 99%
See 1 more Smart Citation
“…Another good example of incremental root scanning is Siebert's approach [93]. As it is a part of a collector which can provide a certain degree of real-time guarantees, it will be introduced along with the collector in the next section.…”
Section: Incremental Root Scanningmentioning
confidence: 99%
“…Siebert published several papers and a thesis to present his unique Dijkstra style write barrier based incremental mark-sweep garbage collector which is claimed to be real-time [90,91,89,92,93,95,94]. One of his two major contributions is the introduction of a new way to eliminate fragmentation.…”
Section: Siebert's Algorithmmentioning
confidence: 99%
“…Memory management mechanisms, such as dynamic memory allocators [26] and garbage collectors [48], can introduce additional unpredictable overheads. On top of this, address space layout randomization and the physical page allocation mechanism change the logical and physical memory layout of the application every time it is executed, potentially affecting the number of conflict misses in the CPU caches and branch mispredictions [17,38].…”
Section: Introductionmentioning
confidence: 99%
“…Techniques for accurate stack scanning in uncooperative environments have been previously described in detail in [13,8]. Popular techniques for conservative garbage collection include the Boehm-Weiser collector [2] and various incarnations of mostly-copying collectors [14,15,16].…”
Section: Related Workmentioning
confidence: 99%
“…JamaicaVM uses explicit pointer stacks [13], but they differ from our implementation. First, objects referenced from the stack cannot move (in Ovm they can).…”
Section: Related Workmentioning
confidence: 99%