Patents
Literature
1 results about "Software transactional memory" patented technology
Efficacy Topic
Property
Owner
Technical Advancement
Application Domain
Technology Topic
Technology Field Word
Patent Country/Region
Patent Type
Patent Status
Application Year
Inventor
In computer science, software transactional memory (STM) is a concurrency control mechanism analogous to database transactions for controlling access to shared memory in concurrent computing. It is an alternative to lock-based synchronization. STM is a strategy implemented in software, rather than as a hardware component. A transaction in this context occurs when a piece of code executes a series of reads and writes to shared memory. These reads and writes logically occur at a single instant in time; intermediate states are not visible to other (successful) transactions. The idea of providing hardware support for transactions originated in a 1986 paper by Tom Knight. The idea was popularized by Maurice Herlihy and J. Eliot B. Moss. In 1995 Nir Shavit and Dan Touitou extended this idea to software-only transactional memory (STM). Since 2005, STM has been the focus of intense research and support for practical implementations is growing.
Concurrency Management Model Using Software Transactional Memory, Dynamic Data Race Detection, And / Or Thread-Local Garbage Collection
PendingUS20260178397A1Memory architecture accessing/allocationResource allocationEngineeringTerm memory
Techniques for detecting and preventing potential sources of concurrency issues are disclosed. In response to an attempt to modify a shared data structure, the system generates a copy of the shared data structure in a transaction area allocated for performing the modification through a software memory transaction. The system applies the modification to the copy of the shared data structure, and the system subsequently acquires a lock on the shared data structure. After acquiring the lock, the system checks for accesses to the shared data structure that would conflict with applying the modification to shared data structure. If the check does not reveal a conflicting access, the system commits the software memory transaction by updating the shared data structure to match the state of the copy of the shared data structure. If the check does reveal a conflicting access, the system aborts the software memory transaction.
Owner:ORACLE INT CORP