2002
DOI: 10.1007/3-540-36108-1_23
|View full text |Cite
|
Sign up to set email alerts
|

The Repeat Offender Problem: A Mechanism for Supporting Dynamic-Sized, Lock-Free Data Structures

Abstract: Abstract:We define the Repeat Offender Problem (ROP). Elsewhere, we have presented the first dynamic-sized lock-free data structures that can free memory to any standard memory allocator-even after thread failures-without requiring special support from the operating system, the memory allocator, or the hardware. These results depend on a solution to the ROP problem. Here we present the first solution to the ROP problem and its correctness proof. Our solution is implementable in most modern shared memory multip… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
98
0

Year Published

2002
2002
2017
2017

Publication Types

Select...
6
2
1

Relationship

1
8

Authors

Journals

citations
Cited by 80 publications
(98 citation statements)
references
References 14 publications
(34 reference statements)
0
98
0
Order By: Relevance
“…Due to space constraints, the development for epochs is deferred to [7, §D]. As far as we know, the only other algorithm that allows explicitly returning memory to the OS in non-blocking algorithms is the Repeat-Offender algorithm [8]. Our preliminary investigations show that our method is applicable to it as well; we leave formalisation for future work.…”
Section: Introductionmentioning
confidence: 99%
“…Due to space constraints, the development for epochs is deferred to [7, §D]. As far as we know, the only other algorithm that allows explicitly returning memory to the OS in non-blocking algorithms is the Repeat-Offender algorithm [8]. Our preliminary investigations show that our method is applicable to it as well; we leave formalisation for future work.…”
Section: Introductionmentioning
confidence: 99%
“…Inter-stage fairness follows from Java thread execution fairness. While the current implementation uses synchronization around the use Java's LinkedList class for a mailbox, performance may potentially be further improved by using lock-free data structures [14,[21][22][23][24], which will be investigated as future work.…”
Section: Safe Message Passingmentioning
confidence: 99%
“…Our demands on the memory management consequently rules out the SMR or ROP methods by Michael [26,27] and Herlihy et al [28] respectively, as they can only guarantee a limited number of nodes to be safe, and these guarantees are also related to individual threads and never to an individual node structure. However, stronger memory management schemes, as for example reference counting, would be sufficient for our needs.…”
Section: Memory Managementmentioning
confidence: 99%