1993
DOI: 10.1109/88.260295
|View full text |Cite
|
Sign up to set email alerts
|

Multiple reservations and the Oklahoma update

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
52
0

Year Published

1998
1998
2013
2013

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 70 publications
(54 citation statements)
references
References 9 publications
0
52
0
Order By: Relevance
“…Ideas similar to the definition of transactional memory can also be found in the Oklahoma Update system [96]. They propose to update multiple shared variables atomically, supporting the "all or nothing" property.…”
Section: General Transactional Memory Terminologymentioning
confidence: 98%
See 1 more Smart Citation
“…Ideas similar to the definition of transactional memory can also be found in the Oklahoma Update system [96]. They propose to update multiple shared variables atomically, supporting the "all or nothing" property.…”
Section: General Transactional Memory Terminologymentioning
confidence: 98%
“…The limitations can be in both space and time. Space related limitations to handle may be, e.g., a limited number of entries in the undo log or write buffer [49], support for only a limited number of updates [96], or no support for nested transactions [70]. Time related limitations to handle include, e.g., context switches, process migration, and other types of interrupts such as page faults.…”
Section: Virtualization Of Hardware Transactional Memorymentioning
confidence: 99%
“…for parallelizing the execution of mostly functional programs [3] or for the management of concurrent access to virtual memory [4]. The HTM mentioned in this paper was firstly proposed in 1993 by [5] and concurrently by [6]. However, the HTM becomes a popular research topic only in recent years after multi-core system is agreed to be the trend of chip design.…”
Section: Related Workmentioning
confidence: 99%
“…On cache overflows, VTM writes the new (and a second copy of old) values to an in-memory table (XADT). VTM does not specify version management when data fits in cache, but rather recommends other proposals [2,11,14,24,30]. [2] proposes using both eager version management and eager conflict detection.…”
Section: Introductionmentioning
confidence: 99%