𝔖 Bobbio Scriptorium
✦   LIBER   ✦

Scalable scheduling for symmetric multiprocessors (SMP)

✍ Scribed by Oh-Han Kang; Dharma P. Agrawal


Book ID
104344641
Publisher
Elsevier Science
Year
2003
Tongue
English
Weight
737 KB
Volume
63
Category
Article
ISSN
0743-7315

No coin nor oath required. For personal study only.

✦ Synopsis


We present a task duplication-based scalable scheduling algorithm for Symmetric Multiprocessors (SMP), called S3MP (Scalable Scheduling for SMP), to address the problem of task scheduling. The algorithm pre-allocates network communication resources so as to avoid potential communication conflicts, and generates a schedule for the number of processors available in a SMP. This algorithm employs heuristics to select duplication of tasks so that schedule length is reduced/minimized. The algorithm can schedule the tasks of a directed acyclic graph (DAG) on to the processors of SMP with a worst case time complexity OðV 2 Þ; where V is the number nodes of the DAG. The performance of the S3MP algorithm has been observed by comparing the schedule length under various number of processors and the ratio of communication to computation cost. This algorithm also has been applied to some practical DAGs.


πŸ“œ SIMILAR VOLUMES


Simple: A Methodology for Programming Hi
✍ David A. Bader; Joseph JΓ‘JΓ‘ πŸ“‚ Article πŸ“… 1999 πŸ› Elsevier Science 🌐 English βš– 252 KB

We describe a methodology for developing high performance programs running on clusters of SMP nodes. The SMP cluster programming methodology is based on a small prototype kernel (Simple) of collective communication primitives that make efficient use of the hybrid shared and message-passing environme

Scheduling algorithm for nonpreemptive m
✍ J.-F. Lin; S.-J. Chen πŸ“‚ Article πŸ“… 1994 πŸ› Elsevier Science 🌐 English βš– 619 KB

This paper considers the problem of scheduling nonpreemptive multiprocessor tasks in a homogeneous system of processors. The problem proposed in this paper is different from the conventional scheduling problem, where each task requires only "one" processor whenever it is in processing. In our multip