|
|
@@ -38,6 +38,8 @@ express that there is a CUDA implementation, even if one does not actually
|
|
|
provide it. StarPU will not actually run it in Simgrid mode anyway by default
|
|
|
(unless the ::STARPU_CODELET_SIMGRID_EXECUTE flag is set in the codelet)
|
|
|
|
|
|
+\snippet simgrid.c To be included. You should update doxygen if you see this text.
|
|
|
+
|
|
|
\section Calibration Calibration
|
|
|
|
|
|
The idea is to first compile StarPU normally, and run the application,
|
|
|
@@ -166,8 +168,6 @@ application running with simgrid, pass the <c>--cfg=contexts/factory:thread</c>
|
|
|
option to the application, to make simgrid use system threads, which gdb will be
|
|
|
able to manipulate as usual.
|
|
|
|
|
|
-\snippet simgrid.c To be included. You should update doxygen if you see this text.
|
|
|
-
|
|
|
\section SimulationMemoryUsage Memory Usage
|
|
|
|
|
|
Since kernels are not actually run and data transfers are not actually
|
