2010 International Conference on Complex, Intelligent and Software Intensive Systems 2010
DOI: 10.1109/cisis.2010.67
|View full text |Cite
|
Sign up to set email alerts
|

A Simple Improvement of the Work-stealing Scheduling Algorithm

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2010
2010
2018
2018

Publication Types

Select...
4
1

Relationship

2
3

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 11 publications
0
5
0
Order By: Relevance
“…The implication of the very different behaviors observed on the different microarchitectures is a demand for scheduling that can adapt to varying conditions using instrumentation data collected at runtime. Our next step is therefore to design such a low-level scheduler in the context of our P2G processing framework [7] using our improvements for the work-stealing approach as a starting point [17].…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…The implication of the very different behaviors observed on the different microarchitectures is a demand for scheduling that can adapt to varying conditions using instrumentation data collected at runtime. Our next step is therefore to design such a low-level scheduler in the context of our P2G processing framework [7] using our improvements for the work-stealing approach as a starting point [17].…”
Section: Discussionmentioning
confidence: 99%
“…In this work, we have identified several challenges with respect to low level scheduling. The de facto standard is a variant of work-stealing scheduling [2], for which we have earlier proposed modifications [17]. We see challenges that have not been addressed by this, and in our work of designing an efficient scheduler, we investigate in this paper how to structure parallel execution of multimedia filters to maximize the performance on several modern architectures.…”
Section: Introductionmentioning
confidence: 99%
“…front [ 2] front [ 1] M task objects Figure 2. Data structure organization of our framework status of all task objects.…”
Section: Front[ N]mentioning
confidence: 99%
“…And two of the three are ubiquitous in all pipeline applications: first, any load imbalances in the pipeline reduce its performance; second, the concurrency in a pipeline is tightly coupled with the set of chosen stages, so the using of more processors may require the pipeline structure be changed to rebalance it. We use work-stealing [1][2][3] technique to implement a load balancing scheduler which would address these two problems. The work-stealing is a widely used load balancing algorithm.…”
Section: Introductionmentioning
confidence: 99%
“…They are caused by high contention over run-queues when stealing. We have therefore modified the work-stealing algorithm so that an unblocked KP is placed on the last CPU that executed it [41] (WS-LAST). We do not use the non-blocking queue described in [4]; instead we use an ordinary mutex per run-queue.…”
Section: Scheduling Policiesmentioning
confidence: 99%