Declarative aspects of memory management in the concurrent collections parallel programming model

  • Authors:

  • Zoran Budimlic;Aparna M. Chandramowlishwaran;Kathleen Knobe;Geoff N. Lowney;Vivek Sarkar;Leo Treggiari

  • Affiliations:

  • Rice University, Houston, TX, USA;Georgia Institute of Technology, Atlanta, GA, USA;Intel Corporation, Cambridge, MA, USA;Intel Corporation, Houston, MA, USA;Rice University, Houston, TX, USA;Intel Corporation, Santa Clara, CA, USA

  • Venue:
  • Proceedings of the 4th workshop on Declarative aspects of multicore programming
  • Year:
  • 2009

Quantified Score

Hi-index 0.00

Visualization

Abstract

Concurrent Collections (CnC) is a declarative parallel language that allows the application developer to express their parallel application as a collection of high-level computations called steps that communicate via single-assignment data structures called items. A CnC program is specified in two levels. At the bottom level, an existing imperative language implements the computations within the individual computation steps. At the top level, CnC describes the relationships (ordering constraints) among the steps. The memory management mechanism of the existing imperative language manages data whose lifetime is within a computation step. A key limitation in the use of CnC for long-running programs is the lack of memory management and garbage collection for data items with lifetimes that are longer than a single computation step. Although the goal here is the same as that of classical garbage collection, the nature of problem and therefore nature of the solution is distinct. The focus of this paper is the memory management problem for these data items in CnC. We introduce a new declarative slicing annotation for CnC that can be transformed into a reference counting procedure for memory management. Preliminary experimental results obtained from a Cholesky example show that our memory management approach can result in space reductions for CnC data items of up to 28x relative to the baseline case of standard CnC without memory management.