2013
DOI: 10.1007/978-3-642-39955-8_4
|View full text |Cite
|
Sign up to set email alerts
|

Handling Parallelism in a Concurrency Model

Abstract: Programming models for concurrency are optimized for dealing with nondeterminism, for example to handle asynchronously arriving events. To shield the developer from data race errors effectively, such models may prevent shared access to data altogether. However, this restriction also makes them unsuitable for applications that require data parallelism. We present a library-based approach for permitting parallel access to arrays while preserving the safety guarantees of the original model. When applied to SCOOP,… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2014
2014
2016
2016

Publication Types

Select...
2
2

Relationship

3
1

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 6 publications
0
4
0
Order By: Relevance
“…In future work, we plan to improve the efficiency of D-SCOOP with respect to intraobject parallelism [11,13]. We will investigate concepts such as slicing [22], and the possible integration of software transactional memory [9]. We will also investigate whether performance can be improved, by (safely) relaxing the requirement that one node communicates with another via a single connection.…”
Section: Discussionmentioning
confidence: 99%
“…In future work, we plan to improve the efficiency of D-SCOOP with respect to intraobject parallelism [11,13]. We will investigate concepts such as slicing [22], and the possible integration of software transactional memory [9]. We will also investigate whether performance can be improved, by (safely) relaxing the requirement that one node communicates with another via a single connection.…”
Section: Discussionmentioning
confidence: 99%
“…Schill et al [25] developed a library offering indexed arrays that can be accessed concurrently by multiple SCOOP processors. To prevent data races on an array, each processor must reserve a slice of the array.…”
Section: Related Workmentioning
confidence: 99%
“…Some languages and libraries [8,16,19,25] have already combined mutually exclusive shared data with message passing and observed performance gains on shared memory systems. However, as discussed in Section 6, these approaches either impose restrictions on the shared data or do not provide unified primitives for data access and message passing.…”
Section: Introductionmentioning
confidence: 99%
“…The original monitor concept [13], where a monitor protects all its associated shared resources (its attributes), follows the idea to make the connection between locks and resources explicit. Message-passing programming models, such as the Actor model [12] or SCOOP [20], simply avoid incorrect memory access by not sharing state; in dataintensive parallel applications, this approach incurs much data messaging overhead, which might be prohibitive unless combined with other techniques [24]. Our approach applies to shared-memory environments.…”
Section: Related Workmentioning
confidence: 99%