X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/767a7a537b2ac742705d23b8dcb25d64cd36a2ee..756b82fad06ba482ed401f3ed35c31874f367e8a:/examples/msg/actions-comm/actions-comm.c

diff --git a/examples/msg/actions-comm/actions-comm.c b/examples/msg/actions-comm/actions-comm.c
index 0d2d6461a4..da5e79f0a8 100644
--- a/examples/msg/actions-comm/actions-comm.c
+++ b/examples/msg/actions-comm/actions-comm.c
@@ -10,21 +10,20 @@
 
 /** @addtogroup MSG_examples
  *
- *  @section MSG_ex_actions Trace driven simulations
+ *  @section msg_ex_actions Trace driven simulations
  * 
- *  The <b>actions/actions.c</b> example demonstrates how to run trace-driven simulations. It is very handy when you
- *  want to test an algorithm or protocol that does nothing unless it receives some events from outside. For example,
- *  a P2P protocol reacts to requests from the user, but does nothing if there is no such event.
+ *  This section details how to run trace-driven simulations. It is very handy when you  want to test an algorithm or
+ *  protocol that does nothing unless it receives some events from outside. For example, a P2P protocol reacts to
+ *  requests from the user, but does nothing if there is no such event.
  * 
- *  In such situations, SimGrid allows to write your protocol in your C file, and the events to react to in a separate
+ *  In such situations, SimGrid allows you to write your protocol in a C file, and the events to react to in a separate
  *  text file. Declare a function handling each of the events that you want to accept in your trace files, register
  *  them using \ref xbt_replay_action_register in your main, and then use \ref MSG_action_trace_run to launch the
  *  simulation. You can either have one trace file containing all your events, or a file per simulated process. Check
- *  the tesh files in the example directory for details on how to do it.
+ *  the tesh files in the example directories for details on how to do it.
  *
- *  This example uses this approach to replay MPI-like traces. It comes with a set of event handlers reproducing MPI
- *  events. This is somehow similar to SMPI, yet differently implemented. This code should probably be changed to use
- *  SMPI internals instead, but wasn't, so far.
+ *  - <b>Communication: actions-comm/actions-comm.c</b>. This example comes with a set of event handlers reproducing
+ *  some classical communication primitives (synchronous and asynchronous send/receive, broadcast, barrier, ...).
  */
 
 XBT_LOG_NEW_DEFAULT_CATEGORY(actions, "Messages specific for this msg example");
@@ -35,8 +34,6 @@ static void action_Isend(const char *const *action);
 typedef struct {
   int last_Irecv_sender_id;
   int bcast_counter;
-  int reduce_counter;
-  int allReduce_counter;
   xbt_dynar_t isends;           /* of msg_comm_t */
   /* Used to implement irecv+wait */
   xbt_dynar_t irecvs;           /* of msg_comm_t */