Difference between revisions of "MPI+Argobots"

From Mpich
Jump to: navigation, search
Line 3: Line 3:
 
[https://collab.mcs.anl.gov/display/ARGOBOTS/Argobots+Home Argobots] is a low-level threading/task infrastructure developed by a joint effort of Argonne National Laboratory, University of Illinois at Urbana-Champaign, University of Tennessee, Knoxville and Pacific Northwest National Laboratory. It provides a lightweight execution model that combines low-latency thread and task scheduling with optimized data-movement functionality.
 
[https://collab.mcs.anl.gov/display/ARGOBOTS/Argobots+Home Argobots] is a low-level threading/task infrastructure developed by a joint effort of Argonne National Laboratory, University of Illinois at Urbana-Champaign, University of Tennessee, Knoxville and Pacific Northwest National Laboratory. It provides a lightweight execution model that combines low-latency thread and task scheduling with optimized data-movement functionality.
  
A benefit of Argobots is providing asynchrony/overlap with ULTs to MPI. The idea is to make multiple MPI blocking calls at the same time in multiple ULTs, if one MPI call is blocked in ULT A, MPI runtime will detect it and context switch to another ULT to make progress on other blocking calls. Once other ULTs finished their execution, they will switch back to ULT A to continue its execution. In this way, we can keep the CPU busy doing useful work instead of waiting the blocking call.
+
A benefit of Argobots is providing asynchrony/overlap to MPI. The idea is to make multiple MPI blocking calls at the same time in multiple ULTs, if one MPI call is blocked in ULT A, MPI runtime will detect it and context switch to another ULT to make progress on other blocking calls. Once other ULTs finished their execution, they will switch back to ULT A to continue its execution. In this way, we can keep the CPU busy doing useful work instead of waiting the blocking call.
  
 
However, the two-level parallelism of MPI+X introduces new problems such as lock contention in MPI between threads. To avoid unnecessary locks between execution units, MPI+Argobots will explicitly control the context switch between User Level Threads (ULT) and Execution Streams (ES). When switching between ULTs in the same ES, no lock is needed.
 
However, the two-level parallelism of MPI+X introduces new problems such as lock contention in MPI between threads. To avoid unnecessary locks between execution units, MPI+Argobots will explicitly control the context switch between User Level Threads (ULT) and Execution Streams (ES). When switching between ULTs in the same ES, no lock is needed.

Revision as of 17:49, 15 December 2014

As core number of CPU processors keeps increasing, MPI+X becomes a promising programming model for large scale SMP clusters. It has the potential to utilizing both intra-node and inter-node parallelism with appropriate execution unit and granularity.

Argobots is a low-level threading/task infrastructure developed by a joint effort of Argonne National Laboratory, University of Illinois at Urbana-Champaign, University of Tennessee, Knoxville and Pacific Northwest National Laboratory. It provides a lightweight execution model that combines low-latency thread and task scheduling with optimized data-movement functionality.

A benefit of Argobots is providing asynchrony/overlap to MPI. The idea is to make multiple MPI blocking calls at the same time in multiple ULTs, if one MPI call is blocked in ULT A, MPI runtime will detect it and context switch to another ULT to make progress on other blocking calls. Once other ULTs finished their execution, they will switch back to ULT A to continue its execution. In this way, we can keep the CPU busy doing useful work instead of waiting the blocking call.

However, the two-level parallelism of MPI+X introduces new problems such as lock contention in MPI between threads. To avoid unnecessary locks between execution units, MPI+Argobots will explicitly control the context switch between User Level Threads (ULT) and Execution Streams (ES). When switching between ULTs in the same ES, no lock is needed.

Build MPI+Argobots

Build Argobots

Follow the instructions in https://collab.mcs.anl.gov/display/ARGOBOTS/Getting+and+Building to build Argobots.

$ export INSTALL_PATH=/path/to/install
$ git clone --origin argobots git://git.mcs.anl.gov/argo/argobots.git argobots
$ cd argobots
$ ./autogen.sh
$ ./configure --prefix=$INSTALL_PATH
$ make -j 4
$ make install

Build MPICH

MPI+Argobots is currently under develop in mpich-dev repository. To get the source code of mpich+argobots, do

$ git clone --origin mpich-dev git://git.mpich.org/mpich-dev.git mpich-dev
$ cd mpich-dev
$ git checkout mpi-argobots
$ ./autogen.sh
$ CFLAGS="-I$INSTALL_PATH/include" ./configure --prefix=$INSTALL_PATH --enable-threads=multiple --with-thread-package=argobots
$ make -j 8
$ make install