- \ref m_process_management
- \ref m_host_management
- \ref m_task_management
+ - \ref msg_mailbox_management
- \ref msg_file_management
- \ref msg_task_usage
- \ref msg_VMs
#MSG_function_register (and maybe #MSG_function_register_default)
-# Launch your processes from a deployment file with #MSG_launch_application
-# Run the simulation with #MSG_main
- -# Cleanup the library with #MSG_clean before ending your program
- (optional).
@htmlonly <!-- DOXYGEN_NAVBAR_LABEL="Simulation Control" --> @endhtmlonly
*/
* \htmlonly <!-- DOXYGEN_NAVBAR_LABEL="Tasks" --> \endhtmlonly
*/
+/** @defgroup msg_mailbox_management Mailbox Management Functions
+ * @ingroup MSG_API
+ * @brief This section describes the mailbox structure of MSG
+ * (#msg_mailbox_t) and the functions for managing it.
+ *
+ * \htmlonly <!-- DOXYGEN_NAVBAR_LABEL="Mailbox" --> \endhtmlonly
+ */
+
/** @defgroup msg_task_usage Task Actions
* @ingroup MSG_API
- * @brief This secti on describes the functions that can be used
+ * @brief This section describes the functions that can be used
* by a process to execute, communicate or otherwise handle some task.
*/
In such situations, SimGrid allows to write your protocol in your 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 #MSG_action_register in your main,
+trace files, register them using #xbt_replay_action_register in your main,
and then use #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.
