Home

About

Advanced Search

Browse by Discipline

Scientific Societies

E-print Alerts

Add E-prints

E-print Network
FAQHELPSITE MAPCONTACT US


  Advanced Search  

 
Hardware Transactional Memory with Software-Defined Conflicts
 

Summary: Hardware Transactional Memory
with Software-Defined Conflicts
Rub´en Titos-Gil Manuel E. Acacio Jos´e M. Garc´ia Tim Harris
Adri´an Cristal Osman Unsal Ibrahim Hur Mateo Valero
Universidad de Murcia
Microsoft Research
Barcelona Supercomputing Center
IIIA - Artificial Intelligence Research Institute CSIC - Spanish National Research Council
{rtitos,meacacio,jmgarcia}@ditec.um.es tharris@microsoft.com
{adrian.cristal,osmal.unsal,ibrahim.hur,mateo.valero}@bsc.es
Abstract
In this paper we propose conflict-defined blocks, a programming language construct that allows programmers to change the
concept of conflict from one transaction to another, or even throughout the course of the same transaction. Defining conflicts in
software makes possible the removal of dependencies which, though not necessary for the correct execution of the transactions,
arise as a result of the coarse synchronization style encouraged by TM. Programmers take advantage of their knowledge
about the problem and specify through confict-defined blocks what types of dependencies are superfluous in a certain part
of the transaction, in order to extract more performance out of coarse-grained transactions without having to write minimally
synchronized code. Our experiments with several transactional benchmarks reveal that using software-defined conflicts, the
programmer achieves significant reductions in the number of aborted transactions and improve scalability.
Permission to make digital or hard copies of all or part of this work for personal or

  

Source: Acacio, Manuel - Departamento de Ingenieria y Tecnologia de Computadores, Universidad de Murcia

 

Collections: Computer Technologies and Information Sciences