Topic
Transactional memory
About: Transactional memory is a research topic. Over the lifetime, 2365 publications have been published within this topic receiving 60818 citations.
Papers published on a yearly basis
Papers
More filters
•
1 citations
••
IBM1
TL;DR: Many shared memory concurrent algorithms involve accessing dynamic nodes of shared structures optimistically, where a thread may access dynamic nodes while they are being updated by concurrent threads.
Abstract: Many shared memory concurrent algorithms involve accessing dynamic nodes of shared structures optimistically, where a thread may access dynamic nodes while they are being updated by concurrent threads Optimistic access is often necessary to enable non-blocking progress, and it is desirable for increasing concurrency and reducing conflicts among concurrent operations.
1 citations
•
09 Mar 2016
TL;DR: In this article, a conflict detection method for transactional memory, a transactional system and a microprocessor is presented, which is based on read-write association among the transactions.
Abstract: The embodiment of the invention provides a conflict detection method for a transactional memory, a transactional memory system and a microprocessor. The method comprises the following steps: during execution of an access operation of a first transaction, recording a read operation of the first transaction in a read set of the first transaction, and recording a write operation of the first transaction in a write set of the first transaction; and after finishing the execution of the first transaction, judging that a conflict exists between the first transaction and a second transaction if intersection sets between the write set of the first transaction and a read set of the second transaction are detected, wherein an execution ending time of the first transaction is ahead of an execution ending time of the second transaction. Through adoption of the conflict detection method for the transactional memory, the transactional memory system and the microprocessor provided by the embodiment of the invention, a relationship between a read set of a transaction ending firstly and a write set of a transaction ending secondly does not need to be compared, so that the problem of transactional conflicts caused by read-write association among the transactions is solved; the probability of the occurrence of conflicts among the transactions is lowered; and the performance of the transactional memory system is enhanced.
1 citations
•
IBM1
TL;DR: In this paper, a deferral instruction associated with a transaction is executed in a transaction execution computing environment with transactional memory, and the progress of the transaction may be monitored during the deferral period.
Abstract: A deferral instruction associated with a transaction is executed in a transaction execution computing environment with transactional memory. Based on executing the deferral instruction, a processor sets a defer-state indicating that pending disruptive events such as interrupts or conflicting memory accesses are to be deferred. A pending disruptive event is deferred based on the set defer-state, and the transaction is completed based on the disruptive event being deferred. The progress of the transaction may be monitored during a deferral period. The length of such deferral period may be specified by the deferral instruction. Whether the deferral period has expired may be determined based on the monitored progress of the transaction. If the deferral period has expired, the transaction may be aborted and the disruptive event may be processed.
1 citations
••
TL;DR: In this experience report, an evaluation of different techniques to manage concurrency in the context of application servers considers the use of software transactional memory to enable concurrent accesses to shared data across different session beans.
Abstract: In this experience report, we present an evaluation of different techniques to manage concurrency in the context of application servers. Traditionally, using entity beans is considered as the only way to synchronize concurrent access to data in Jave EE and using mechanism such as synchronized blocks within EJBs is strongly not recommended. In our evaluation we consider the use of software transactional memory to enable concurrent accesses to shared data across different session beans. We are also comparing our approach with using (1) entity beans and (2) session beans synchronized by a global lock.
1 citations