Introduction - If you have any usage issues, please Google them yourself
ABSTRACT
The advent of multicore processors has renewed interest in the idea of incorporating transactions
into the programming model used to write parallel programs. This approach, known
as transactional memory, offers an alternative, and hopefully better, way to coordinate concurrent
threads. The ACI (atomicity, consistency, isolation) properties of transactions provide a
foundation to ensure that concurrent reads and writes of shared data do not produce inconsistent
or incorrect results. At a higher level, a computation wrapped in a transaction executes
atomically – either it completes successfully and commits its result in its entirety or it aborts. In
addition, isolation ensures the transaction produces the same result as if no other transactions
were executing concurrently.
Although transactions are not a parallel programming panacea, they shift much of the
burden of synchronizing and coordinating parallel computations from a programmer to a compiler,
runtime system,