ACM Home Page
Please provide us with feedback. Feedback
The transactional memory / garbage collection analogy
Full text PdfPdf (185 KB)
Source
Conference on Object Oriented Programming Systems Languages and Applications archive
Proceedings of the 22nd annual ACM SIGPLAN conference on Object-oriented programming systems and applications table of contents
Montreal, Quebec, Canada
SESSION: Essays session 2 table of contents
Pages: 695 - 706  
Year of Publication: 2007
ISBN:978-1-59593-786-5
Also published in ...
Author
Dan Grossman  University of Washington, Seattle, WA
Sponsors
SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 26,   Downloads (12 Months): 206,   Citation Count: 5
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1297027.1297080
What is a DOI?

ABSTRACT

This essay presents remarkable similarities between transactional memory and garbage collection. The connections are fascinating in their own right, and they let us better understand one technology by thinking about the corresponding issues for the other.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
2
 
3
E. Allen, D. Chase, J. Hallet, V. Luchangco, J.-W. Maessen, S. Ryu, G. L. Steele Jr., and STobin-Hochstadt. The Fortress language specification, version 1.0β, Mar. 2007. http://research.sun.com/projects/plrg/fortress1.0beta.pdf.
 
4
5
 
6
G. Bellella, editor. The Real-Time Specification for Java. Addison-Wesley, 2000.
7
 
8
9
10
 
11
Cray Inc. Chapel specification 0.4. http://chapel.cs.washington.edu/specification.pdf.
12
13
 
14
R. Ennals. Software transactional memory should not be lock free. Technical Report IRC-TR-06-052, Intel Research Cambridge, 2006. http://berkeley.intel-research.net/rennals/pubs/052RobEnnals.pdf.
15
16
 
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
 
33
34
 
35
J. R. Larus and R. Rajwar. Transactional Memory. Morgan & Claypool Publishers, 2006.
 
36
 
37
V. J. Marathe, W. N. Scherer, and M. L. Scott. Adaptive software transactional memory. In International Symposium on Distributed Computing, 2005.
38
39
 
40
K. E. Moore, J. Bobba, M. J. Moravan, M. D. Hill, and D. A. Wood. LogTM: Log-based transactional memory. In 12th International Symposium on High- Performance Computer Architecture, 2006.
41
42
 
43
44
 
45
N. Shavit and D. Touitou. Software transactional memory. Distributed Computing, Special Issue(10), 1997.
46
 
47
 
48
P. R. Wilson. Uniprocessor garbage collection techniques. Technical report, University of Texas, 1994.
49