X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/e7f5fb72d24ece31c4edc5693cf4626658552041..22cae46149e1fb4988ad9e46060c3e7ecd4e0e44:/doc/doxygen/module-smpi.doc
diff --git a/doc/doxygen/module-smpi.doc b/doc/doxygen/module-smpi.doc
index 5fe713d13a..811a399a71 100644
--- a/doc/doxygen/module-smpi.doc
+++ b/doc/doxygen/module-smpi.doc
@@ -63,7 +63,7 @@ SMPI_PRETEND_CC=1 ./configure # here come the configure parameters
make
@endverbatim
-\warn
+\warning
Again, make sure that SMPI_PRETEND_CC is not set when you actually
compile your application. It is just a work-around for some configure-scripts
and replaces some internals by "return 0;". Your simulation will not
@@ -156,6 +156,7 @@ Most of these are best described in this paper
- 2dmesh: organizes the nodes as a two dimensional mesh, and perform allgather
along the dimensions
- 3dmesh: adds a third dimension to the previous algorithm
@@ -485,7 +486,7 @@ SimGrid can duplicate and dynamically switch the .data and .bss
segments of the ELF process when switching the MPI ranks, allowing
each ranks to have its own copy of the global variables. This feature
is expected to work correctly on Linux and BSD, so smpirun activates
-it by default. %As no copy is involved, performance should not be
+it by default. As no copy is involved, performance should not be
altered (but memory occupation will be higher).
If you want to turn it off, pass \c -no-privatize to smpirun. This may
@@ -527,7 +528,7 @@ area between processes does not seem very wise. You cannot use the
SMPI_SHARED_MALLOC macro in this case, sorry.
This feature is demoed by the example file
-examples/smpi/NAS/DT-folding/dt.c
+examples/smpi/NAS/dt.c
@subsection SMPI_adapting_speed Toward faster simulations
@@ -541,7 +542,7 @@ SMPI_SAMPLE_GLOBAL. Of course, none of this will work if the execution
time of your loop iteration are not stable.
This feature is demoed by the example file
-examples/smpi/NAS/EP-sampling/ep.c
+examples/smpi/NAS/ep.c
@section SMPI_accuracy Ensuring accurate simulations
@@ -569,7 +570,7 @@ precious for that). Then, try to modify your model (of the platform,
of the collective operations) to reduce the most preeminent differences.
If the discrepancies come from the computing time, try adapting the \c
-smpi/running-power: reduce it if your simulation runs faster than in
+smpi/host-speed: reduce it if your simulation runs faster than in
reality. If the error come from the communication, then you need to
fiddle with your platform file.