X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/a243b4c3535f516d05259cac06963c422d4aadc0..a6b23c846948f7f89277f75e7c42f3942b31b8d3:/doc/doxygen/platform.doc diff --git a/doc/doxygen/platform.doc b/doc/doxygen/platform.doc index c2712b6756..109d3cbf2e 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 @@ -609,22 +624,37 @@ find /path/you/want -type f -exec ls -l {} \; 2>/dev/null > ./content.txt \li content: default value 0. The file containing the disk content. (may be moved soon or later to storage tag. -The tag must contains some predefined prop, as may do some other -resources tags. This should moved to attributes soon or later. -storage_type mandatory prop : +The tag must contains some predefined model prop, as may do some other +resources tags. +storage_type mandatory model_prop : \li Bwrite: value in B/s. Write throughput \li Bread: value in B/s. Read throughput \li Bconnexion: value in B/s. Connection throughput (i.e. the throughput of the storage connector). +A storage_type can also contain the prop tag. The prop tag allows you +to define additional information on this storage_type following the +attribute/value schema. You may want to use it to give information to +the tool you use for rendering your simulation, for example. + +\verbatim + + + + + + +\endverbatim + \subsubsection pf_sto_st storage storage_type attributes : \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 @@ -938,7 +968,7 @@ Note that when using route to give topological information, you have 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 Note : bypassASroute and bypassRoute are under rewriting to perform better ; so you may not use it yet As said before, once you choose