|
|
@@ -883,13 +883,13 @@ the configure option \ref enable-mpi-master-slave
|
|
|
"--enable-mpi-master-slave". However, you should not activate both MPI
|
|
|
support and MPI Master-Slave support.
|
|
|
|
|
|
-If a codelet contains a kernel for CPU devices, it is automatically eligible to be executed
|
|
|
-on a MPI Slave device. Moreover, you can force the execution on a MPI Slave by setting
|
|
|
-the field \ref starpu_codelet::mpi_ms_funcs. Functions have to be
|
|
|
-globally-visible (i.e. not static) for StarPU to be able to look them
|
|
|
-up, and <c>-rdynamic</c> must be passed to gcc (or
|
|
|
-<c>-export-dynamic</c> to ld) so that symbols of the main program are
|
|
|
-visible.
|
|
|
+The existing kernels for CPU devices can be used as such. They only have to be
|
|
|
+exposed through the name of the function in the \ref starpu_codelet::cpu_funcs_name field.
|
|
|
+Functions have to be globally-visible (i.e. not static) for StarPU to
|
|
|
+be able to look them up, and <c>-rdynamic</c> must be passed to gcc (or
|
|
|
+<c>-export-dynamic</c> to ld) so that symbols of the main program are visible.
|
|
|
+Optionally, you can choose the use of another function on slaves thanks to
|
|
|
+the field \ref starpu_codelet::mpi_ms_funcs.
|
|
|
|
|
|
By default, one core is dedicated on the master node to manage the
|
|
|
entire set of slaves. If the implementation of MPI you are using has a
|
