• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

DMCA

Transactional Memory: Architectural Support for Lock-Free Data Structures

Cached

  • Download as a PDF

Download Links

  • [ocw.mit.edu]
  • [impact.asu.edu]
  • [impact.asu.edu]
  • [impact.asu.edu]
  • [www.cs.brown.edu]
  • [ftp.digital.fr]
  • [courses.cs.vt.edu]
  • [courses.cs.vt.edu]
  • [ftp.cs.umass.edu]
  • [www.hpl.hp.com]
  • [csis.bits-pilani.ac.in]
  • [www.cs.brown.edu]
  • [www.ece.northwestern.edu]
  • [www.cag.csail.mit.edu]
  • [www.cs.brown.edu]
  • [courses.csail.mit.edu]
  • [cs.brown.edu]
  • [www.cs.helsinki.fi]
  • [www.cvorg.ece.udel.edu]
  • [www.cvorg.ece.udel.edu]
  • [cs.brown.edu]

  • Save to List
  • Add to Collection
  • Correct Errors
  • Monitor Changes
by Maurice Herlihy , J. Eliot B. Moss
Citations:1031 - 27 self
  • Summary
  • Citations
  • Active Bibliography
  • Co-citation
  • Clustered Documents
  • Version History

BibTeX

@MISC{Herlihy_transactionalmemory:,
    author = {Maurice Herlihy and J. Eliot B. Moss},
    title = {Transactional Memory: Architectural Support for Lock-Free Data Structures},
    year = {}
}

Share

Facebook Twitter Reddit Bibsonomy

OpenURL

 

Abstract

A shared data structure is lock-free if its operations do not require mutual exclusion. If one process is interrupted in the middle of an operation, other processes will not be prevented from operating on that object. In highly concurrent systems, lock-free data structures avoid common problems associated with conventional locking techniques, including priority inversion, convoying, and difficulty of avoiding deadlock. This paper introduces transactional memory, a new multiprocessor architecture intended to make lock-free synchronization as efficient (and easy to use) as conventional techniques based on mutual exclusion. Transactional memory allows programmers to define customized read-modify-write operations that apply to multiple, independently-chosen words of memory. It is implemented by straightforward extensions to any multiprocessor cache-coherence protocol. Simulation results show that transactional memory matches or outperforms the best known locking techniques for simple benchmarks, even in the absence of priority inversion, convoying, and deadlock.

Keyphrases

transactional memory    lock-free data structure    architectural support    priority inversion    mutual exclusion    data structure    straightforward extension    simulation result    independently-chosen word    transactional memory match    new multiprocessor architecture    lock-free synchronization    conventional technique    concurrent system    common problem    multiprocessor cache-coherence protocol    customized read-modify-write operation    simple benchmark   

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University