Real-time memory management: Life and times

  • Andrew Borg
  • , Andy Wellings
  • , Christopher Gill
  • , Ron K. Cytron

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

15 Scopus citations

Abstract

As real-time and embedded systems become increasingly large and complex, the traditional strictly static approach to memory management begins to prove untenable. The challenge is to provide a dynamic memory model that guarantees tight and bounded time and space requirements without over-burdening the developer with memory concerns. This paper provides an analysis of memory management approaches in order to characterise the tradeoffs across three semantic domains: space, time and a characterisation of memory usage information such as the lifetime of objects. A unified approach to distinguishing the merits of each memory model highlights the relationship across these three domains, thereby identifying the class of applications that benefit from targeting a particular model. Crucially, an initial, investigation of this relationship identifies the direction future research must take in order to address the requirements of the next generation of complex embedded systems. Some initial suggestions are made in this regard and the memory model proposed in the Real-Time Specification for Java is evaluated in this context.

Original languageEnglish
Title of host publicationProceedings - 18th Euromicro Conference on Real-Time Systems, ECRTS 2006
Pages237-247
Number of pages11
DOIs
StatePublished - 2006
Event18th Euromicro Conference on Real-Time Systems, ECRTS 2006 - Dresden, Germany
Duration: Jul 5 2006Jul 7 2006

Publication series

NameProceedings - Euromicro Conference on Real-Time Systems
Volume2006
ISSN (Print)1068-3070

Conference

Conference18th Euromicro Conference on Real-Time Systems, ECRTS 2006
Country/TerritoryGermany
CityDresden
Period07/5/0607/7/06

Fingerprint

Dive into the research topics of 'Real-time memory management: Life and times'. Together they form a unique fingerprint.

Cite this