2004
DOI: 10.1023/b:time.0000009306.22263.59
|View full text |Cite
|
Sign up to set email alerts
|

Memory Management for Real-Time Java: An Efficient Solution using Hardware Support*

Abstract: This paper addresses the issue of improving the performance of memory management for real-time Java applications, building upon the real-time speci®cation for Java (RTSJ) from the Real-Time Java Expert Group. In a ®rst step, a collecting dynamic memory solution including both a real-time garbage collector and region-based memory management, is proposed. A thorough analysis of the parameters in¯uencing the performance of write barriers in memory management, together with ways of improvement are then presented. … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2005
2005
2018
2018

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 23 publications
(11 citation statements)
references
References 13 publications
0
11
0
Order By: Relevance
“…Its response time depends on the total number of reachable objects when it has to collect a non-referenced cycle. [13] propose a picoJava-II hardware implementation of an adaptation of the incremental treadmill algorithm [11]. This approach is not portable and it does not ensure predictable execution times.…”
Section: Introductionmentioning
confidence: 99%
“…Its response time depends on the total number of reachable objects when it has to collect a non-referenced cycle. [13] propose a picoJava-II hardware implementation of an adaptation of the incremental treadmill algorithm [11]. This approach is not portable and it does not ensure predictable execution times.…”
Section: Introductionmentioning
confidence: 99%
“…Note that when using a write-barrier-based GC, read barriers detecting memory access errors are not strictly necessary because read operations do not change the colour of the object, therefore they do not affect the GC coherence [13]. The restriction on critical tasks can be reduced to write barriers checks since reads do not interfere with the GC.…”
Section: The Gc and Mr Interactionmentioning
confidence: 99%
“…Hence, to detect new roots of the GC, instead of employing a technique based on the region to which the objects belong (e.g. as used by generational collectors to maintain inter-generational pointers [12]), we introduce a fourth colour indicating whether an object is outside the heap [13]. Another problem is with the critical tasks that cannot access objects within the heap.…”
Section: Related Workmentioning
confidence: 99%
“…Higuera suggests in [14] the use of hardware features from picoJava [24] to speed up RTSJ memory region protection and garbage collection. A hardware assisted realtime collector is proposed by Schmidt and Nielsen [29].…”
Section: Real-timementioning
confidence: 99%