School of Computer Science Wiki

You've loaded an old revision of the document! If you save it, you will create a new version with this data.

Include a brief summary of the course topics and requirements, the general format of the course, and the methods of evaluation.

== Skills and knowledge students should have prior to beginning the course: ==

* CIS*2030 or ENGG*3640: Successful parallel programming relies on an understanding of the underlying CPU hardware, including how assembly language instructions are executed, and how RAM is organized and referenced.
  * CIS*3110: Certain OS topics are highly relevant to parallel programming, including processes and threads, concurrency, virtual memory, memory hierarchy (caching), scheduling and context switching, deadlocks, race conditions, mutexes, and more. Pthreads programming is normally introduced in an OS course, and will be used for one programming assignment.

== Course Topics: ==

Today's computer science students are entering a new era in parallel computing, featuring cheap multicores and high-performance clusters, but have received traditional largely-sequential training. This paradigm shift has been called "the end of the lazy programmer era." This course is aimed at helping soon-to-graduate students (1) move into jobs using current tools for parallel programming, and (2) acquire the theoretical background needed to keep abreast with rapid industry developments and to evolve with them. The textbook will provide foundational knowledge about modern parallel processor architectures and algorithms for organizing concurrent computations. Since parallel programming is all about speed, we will learn ways to measure execution performance and speedup through parallelization.

In terms of practical skills, high-performance (non-shared memory) cluster programming will be introduced via the University of Guelph Pilot library, based on MPI and utilizing message-passing. Programming for multicore shared memory processors will utilize the popular existing parallel programming technique of POSIX threads, and compiler-based OpenMP, supported by the latest suite of Intel tools, as well as Java threads. Heterogeneous architectures--GPUs (graphics processing units) and the Intel Xeon Phi--will be introduced.

- Historical perspective on concurrency in computing
  - Parallel computer system architectures
    * Abstractions for modeling sequential and parallel computation
    * Homogeneous vs. heterogeneous multiprocessors
    * Shared vs. non-shared memory systems
  - Performance: speedup, Amdahl's Law, measurement, performance losses, difficulties in scaling
  - Abstractions and algorithms for parallel program design: task vs. data parallelism, scalable parallelism, reduce and scan, work assignment
  - Practical programming: message passing, Pilot library, POSIX threads, OpenMP, Java threads
  - Overview of CUDA and OpenACC for GPU programming
  - Overview of Intel Xeon Phi coprocessor
  - Future directions in hardware and software

== Course Format: ==

* Lecture format: YES
  * Online materials location and format: CourseLink and instructor's website
  * Lab or tutorial format and expectations: Weekly lab sessions are primarily used to introduce parallel programming tools and work through hands-on exercises.

== Method of evaluation: ==

* Number of Assignments: 4 (C and Java), or 3 (C) + project (your choice of language)
  * Number of Graded Labs: none
  * Number of Quizzes: 7 (each one open for a week in CourseLink)
  * Formal Midterm: YES in 4-assignments format; NO with project
  * Course project: The course has been offered with and without a project, depending on the number of students. The project requires a class presentation and report (see below).
  * Final Exam: YES
  * Group work: Assignments are strictly individual work. Groups of 2 are permitted for projects.
  * Mostly programming assignments? YES
  * Written documents? YES, each assignment includes a report that (a) shows graphs of the program's parallel performance, and (b) discussion of the program's design, its performance, and use of the language/tools. The project requires a similar report.

Edit summary

Note: By editing this page you agree to license your content under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International