X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/6de03ecc4e630732984a0673512a5d15fd75e270..3fdb26f94c30bb57196c2857db30d0dbdfdddcf1:/doc/doxygen/platform.doc?ds=sidebyside diff --git a/doc/doxygen/platform.doc b/doc/doxygen/platform.doc index 5c3ae9ea82..fd64f878a7 100644 --- a/doc/doxygen/platform.doc +++ b/doc/doxygen/platform.doc @@ -361,12 +361,27 @@ unset. availability. Similar to hosts attribute. \li state_file: Allow you to use a file as input for states. Similar to hosts attribute. +\li loopback_bw : bandwidth for loopback (if any). See link + 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 FATPIPE. +\li loopback_lat : latency for loopback (if any). See link + section for syntax/details. See loopback_bw for more info. +\li topology : network topology to use. For now SimGrid supports FLAT + (default, with or without backbone, as described before), + TORUS + and FAT_TREE attributes for this tag. +\li topo_parameters : 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: @verbatim -router_name = prefix + clusterId + router_ + suffix; +router_name = prefix + clusterId + _router + suffix; @endverbatim @@ -383,11 +398,11 @@ The second examples creates one router and 100 machines, which names 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 @@ -637,8 +652,9 @@ the tool you use for rendering your simulation, for example. \li id (mandatory): the identifier of the storage to be used when referring to it. \li typeId (mandatory): the identifier of the storage_type that - this storage belongs to. - + this storage belongs to. +\li attach (mandatory): the host (name) to which the storage is + attached to. \subsubsection pf_sto_mo mount