In this paper, we present a memory management model for the Ravenscar-Java profile. Because of the complexity and run-time overheads in verifying the proper use of the RTSJs scoped memory, it is unfavourable in the area of high integrity systems where any unpredictability must be cast out. Our approach maps one anonymous memory area to a user-specifiable method by means of our Java 1.5 annotation types. This straightforward model eliminates single parent rule checks and simplifies other run-time checks that are the main cause of unpredictability and overheads. In fact, it also makes the programmers job easier since he/she does not have to worry about creating and maintaining memory areas. All the annotated methods will be automatically converted by a transformer into an RTSJ/Ravenscar-Java compliant version. The semantics of the RTSJ remains the same, meaning that any program in our model when transformed is also a legal RTSJ program. Our key contribution is the definition of a predictable memory model and guidelines that will reduce/eliminate run-time overheads. A bonus to this is a less complicated programming model.

BibTex Entry

@inproceedings{Kwon2004,
 address = {Heidelberg, Germany},
 author = {J. Kwon and A. Wellings},
 booktitle = {Lecture Notes in Computer Science (3292) Proceedings of the OTM 2004 Workshops: Workshop on Java Technologies for Real-Time and Embedded Systems (JTRES)},
 editor = {Z. Tari R. Meersman and A. Corsaro},
 month = {October},
 pages = {333-345},
 publisher = {Springer-Verlag},
 series = {Lecture Notes in Computer Science},
 title = {Memory Management Based on Method Invocation in RTSJ},
 volume = {3292},
 year = {2004}
}