availability. Similar to <b>hosts</b> attribute.
\li <b>state_file</b>: Allow you to use a file as input for states.
Similar to <b>hosts</b> attribute.
+\li <b>loopback_bw </b>: bandwidth for loopback (if any). See <b>link</b>
+ section for syntax/details. If both loopback_* attributes are omitted,
+ no loopback link is created and all intra-node communication will
+ use the main network link of the node. Loopback link is a <b>FATPIPE</b>.
+\li <b>loopback_lat </b>: latency for loopback (if any). See <b>link</b>
+ section for syntax/details. See loopback_bw for more info.
+\li <b>topology </b>: network topology to use. For now SimGrid supports FLAT
+ (default, with or without backbone, as described before),
+ <a href="http://en.wikipedia.org/wiki/Torus_interconnect">TORUS
+ </a> and FAT_TREE attributes for this tag.
+\li <b>topo_parameters </b>: specific parameters to pass for the topology
+ defined in the topology tag. For torus networks, comma-separated list of
+ the number of nodes in each dimension of the torus. For fat trees, refer to
+ \ref AsClusterFatTree "AsClusterFatTree documentation".
+
the router name is defined as the resulting String in the following
java line of code:
are the following:
\verbatim
c-my_cluster_1_router.me
-c-0.my_cluster_1.me
-c-1.my_cluster_1.me
-c-2.my_cluster_1.me
+c-0.me
+c-1.me
+c-2.me
...
-c-99.my_cluster_1.me
+c-99.me
\endverbatim
\subsubsection pf_peer peer
to give routes with one link only in it, as SimGrid needs to know
which host are at the end of the link.
-\subsubsection pf_byro bypassASroute
+\subsubsection pf_byASro bypassASroute
<b>Note : bypassASroute and bypassRoute are under rewriting to perform
better ; so you may not use it yet</b> As said before, once you choose
