Commit 1982c37f authored by Pedro Gonnet's avatar Pedro Gonnet
Browse files

clearer wording on why we built our own task-based library.

parent 50607f0f
...@@ -342,13 +342,14 @@ SMP~Superscalar \cite{ref:SMPSuperscalar}, OpenMP~3.0 \cite{ref:Duran2009}, ...@@ -342,13 +342,14 @@ SMP~Superscalar \cite{ref:SMPSuperscalar}, OpenMP~3.0 \cite{ref:Duran2009},
Intel's TBB \cite{ref:Reinders2007}, and, to some extent, Intel's TBB \cite{ref:Reinders2007}, and, to some extent,
Charm++ \cite{ref:Kale1993}. Charm++ \cite{ref:Kale1993}.
For convenience, and to make experimenting with different scheduling Since none of these existing taks-based libraries provide the flexibility
techniques easier, we chose to implement our own task scheduler required to make experiment with different scheduling and communication
techniques, we chose to implement our own task scheduler
in \swift, which has since been back-ported as the general-purpose in \swift, which has since been back-ported as the general-purpose
\qs task scheduler \cite{gonnet2013quicksched}. \qs task scheduler \cite{gonnet2013quicksched}.
This also allowed us to extend the scheduler with the concept of This also allowed us to extend the scheduler with the concept of
task conflicts and integrate the asynchronous communication task conflicts and integrate the asynchronous communication
scheme described below. scheme described further on.
Despite its advantages, and the variety of implementations, Despite its advantages, and the variety of implementations,
task-based parallelism is rarely used in task-based parallelism is rarely used in
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment