|
@@ -167,8 +167,12 @@ theory results), see the \ref STARPU_SIMGRID_TRANSFER_COST, \ref STARPU_SIMGRID_
|
|
|
|
|
|
|
|
\section SimulationMPIApplications MPI Applications
|
|
\section SimulationMPIApplications MPI Applications
|
|
|
|
|
|
|
|
-StarPU-MPI applications can also be run in SimGrid mode. It needs to be compiled
|
|
|
|
|
-with \c smpicc, and run using the <c>starpu_smpirun</c> script, for instance:
|
|
|
|
|
|
|
+StarPU-MPI applications can also be run in SimGrid mode. smpi currently requires
|
|
|
|
|
+that StarPU be build statically only, so <c>--disable-shared</c> needs to be
|
|
|
|
|
+passed to <c>./configure</c>.
|
|
|
|
|
+
|
|
|
|
|
+The application needs to be compiled with \c smpicc, and run using the
|
|
|
|
|
+<c>starpu_smpirun</c> script, for instance:
|
|
|
|
|
|
|
|
\verbatim
|
|
\verbatim
|
|
|
$ STARPU_SCHED=dmda starpu_smpirun -platform cluster.xml -hostfile hostfile ./mpi/tests/pingpong
|
|
$ STARPU_SCHED=dmda starpu_smpirun -platform cluster.xml -hostfile hostfile ./mpi/tests/pingpong
|
|
@@ -182,6 +186,13 @@ in case of a heterogeneous platform, it is possible to use the
|
|
|
option <c>-hostfile-platform</c> in <c>starpu_smpirun</c>, that will define
|
|
option <c>-hostfile-platform</c> in <c>starpu_smpirun</c>, that will define
|
|
|
\ref STARPU_MPI_HOSTNAMES with the hostnames of your hostfile.
|
|
\ref STARPU_MPI_HOSTNAMES with the hostnames of your hostfile.
|
|
|
|
|
|
|
|
|
|
+So as to use FxT traces, libfxt also needs to be built statically, <b>and</b>
|
|
|
|
|
+with dynamic linking flags, i.e. with
|
|
|
|
|
+
|
|
|
|
|
+\verbatim
|
|
|
|
|
+CFLAGS=-fPIC ./configure --enable-static
|
|
|
|
|
+\endverbatim
|
|
|
|
|
+
|
|
|
\section SimulationDebuggingApplications Debugging Applications
|
|
\section SimulationDebuggingApplications Debugging Applications
|
|
|
|
|
|
|
|
By default, SimGrid uses its own implementation of threads, which prevents \c gdb
|
|
By default, SimGrid uses its own implementation of threads, which prevents \c gdb
|
