1 This file follows the Doxygen syntax to be included in the
2 documentation, but it should remain readable directly.
5 @defgroup msg_examples MSG examples
7 @brief Find the MSG example fitting your needs from the extensive set provided in the archive.
12 - @ref msg_ex_tracing_user_variables
18 @section msg_ex_basics Basic examples and features
21 @ref examples/msg/app-token-ring/app-token-ring.c\n
22 Classical communication pattern, where a token is exchanged
23 along a ring to reach every participant.
24 The tesh file laying in the directory shows how to run the same
25 example on different virtual platforms.
27 - <b>Master Workers</b>.
28 @ref examples/msg/app-masterworker/app-masterworker.c\n
29 Another good old example, where one Master process has a bunch of
30 task to dispatch to a set of several Worker processes. It is fully
31 commented in @ref msg_ex_master_worker.
33 @section msg_ex_process Acting on Processes
35 - <b>Creating processes</b>.
36 @ref examples/msg/process-create/process-create.c \n
37 Most processes are started from the deployment XML file, but they
38 can also be used with the @ref MSG_process_create() function.
40 @section msg_ex_tracing Tracing and visualization features
42 Tracing can be activated by various configuration options which
43 are illustrated in these example. See also the
44 @ref tracing_tracing_options "full list of options related to tracing".
46 It is interesting to run the process-create example with the following
47 options to see the task executions:
49 - <b>Setting Categories</b>.
50 @ref examples/msg/trace-categories/trace-categories.c \n
51 This example declares several tracing categories
52 to that are used to classify its tasks. When the program is executed,
53 the tracing mechanism registers the resource utilization of hosts
54 and links according to these categories. Recommanded options:
55 @verbatim --cfg=tracing:yes --cfg=tracing/categorized:yes --cfg=tracing/uncategorized:yes
58 - <b>Master Workers tracing</b>.
59 @ref examples/msg/trace-masterworker/trace-masterworker.c \n
60 This is an augmented version of our basic master/worker example
61 using several tracing features. It traces resource usage, sorted
62 out in several categories; Trace marks and user variables are also
63 used. Recommanded options:
64 @verbatim --cfg=tracing/categorized:yes --cfg=tracing/uncategorized:yes
67 - <b>Process migration tracing</b>.
68 @ref examples/msg/trace-process-migration/trace-process-migration.c \n
69 This version is enhanced so that the process migrations can be
70 displayed as arrows in a Gantt-chart visualization. Recommanded
71 options to that extend:
72 @verbatim -cfg=tracing:yes --cfg=tracing/msg/process:yes
75 TODO: These tracing examples should be integrated in the examples to
76 not duplicate the C files. A full command line to see the result in
77 the right tool (vite/FrameSoc) should be given along with some
80 @subsection msg_ex_tracing_user_variables Tracing user variables
82 You can also attach your own variables to a any resource described in
83 the platform file. The following examples illustrate this feature.
84 They have to be run with the following options:
85 @verbatim --cfg=tracing:yes --cfg=tracing/platform:yes
88 - <b>Attaching variables to Hosts</b>.
89 @ref examples/msg/trace-host-user-variables/trace-host-user-variables.c
91 - <b>Attaching variables to Links</b>.
92 @ref examples/msg/trace-link-user-variables/trace-link-user-variables.c \n
93 The tricky part is that you have to know the name of the link you
94 want to enhance with a variable.
96 - <b>Attaching variables to network Routes</b>
97 @ref examples/msg/trace-route-user-variables/trace-route-user-variables.c \n
98 It is often easier to update a given variable for all links of a
99 given network path (identified by its source and destination
100 hosts) instead of knowing the name of each specific link.
102 @section msg_ex_models Models-related examples
104 @subsection msg_ex_ns3 NS3 as a SimGrid Network Model
106 This example demonstrates how to use the bindings to the Network
107 Simulator, as explained in @ref pls_ns3. The most
108 interesting is probably not the C files since they are unchanged from
109 the other simulations, but the associated files, such as the platform
110 file to see how to declare a platform to be used with the ns-3 bindings
111 of SimGrid and the tesh file to see how to actually start a simulation
114 - @ref examples/msg/network-ns3/network-ns3.c. Simple ping-pong using
115 ns-3 instead of the SimGrid network models.
117 TODO: merge the C files
119 TODO: show the XML files instead if it's what is interesting. On a "XML example files" page that does not exist yet.
123 As a human, you can stop reading at this point. The rest is garbage:
125 Every example must be listed in the following, but it's not possible
126 to move this content upper as each @example directive seems to eat
127 everything until the next */ marker (and the content is placed at the
128 top of the example file).
132 @example examples/msg/app-token-ring/app-token-ring.c
133 @example examples/msg/app-masterworker/app-masterworker.c
135 @example examples/msg/process-create/process-create.c
137 @example examples/msg/trace-categories/trace-categories.c
138 @example examples/msg/trace-masterworker/trace-masterworker.c
139 @example examples/msg/trace-process-migration/trace-process-migration.c
140 @example examples/msg/trace-host-user-variables/trace-host-user-variables.c
141 @example examples/msg/trace-link-user-variables/trace-link-user-variables.c
142 @example examples/msg/trace-route-user-variables/trace-route-user-variables.c
144 @example examples/msg/network-ns3/network-ns3.c