X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/b6865f6fb60b7de821e9a9716e443f256834f088..f997dd57c10e92aaed05832c96db7348d0da87ed:/doc/doxygen/options.doc diff --git a/doc/doxygen/options.doc b/doc/doxygen/options.doc index 4739cf5def..64ce0db6f5 100644 --- a/doc/doxygen/options.doc +++ b/doc/doxygen/options.doc @@ -42,7 +42,7 @@ file: A last solution is to pass your configuration directly using the C interface. If you happen to use the MSG interface, this is very easy -with the MSG_config() function. If you do not use MSG, that's a bit +with the simgrid::s4u::Engine::setConfig() or MSG_config() functions. If you do not use MSG, that's a bit more complex, as you have to mess with the internal configuration set directly as follows. Check the \ref XBT_config "relevant page" for details on all the functions you can use in this context, \c @@ -73,7 +73,7 @@ int main(int argc, char *argv[]) { - \c contexts/factory: \ref options_virt_factory - \c contexts/guard-size: \ref options_virt_guard_size - \c contexts/nthreads: \ref options_virt_parallel -- \c contexts/parallel_threshold: \ref options_virt_parallel +- \c contexts/parallel-threshold: \ref options_virt_parallel - \c contexts/stack-size: \ref options_virt_stacksize - \c contexts/synchro: \ref options_virt_parallel @@ -112,7 +112,6 @@ int main(int argc, char *argv[]) { - \c network/maxmin-selective-update: \ref options_model_optim - \c network/model: \ref options_model_select - \c network/optim: \ref options_model_optim -- \c network/sender_gap: \ref options_model_network_sendergap - \c network/TCP-gamma: \ref options_model_network_gamma - \c network/weight-S: \ref options_model_network_coefs @@ -317,7 +316,7 @@ setting on regular (less constrained) scenarios so it is off by default. \subsubsection options_model_network_gamma Maximal TCP window size The analytical models need to know the maximal TCP window size to take -the TCP congestion mechanism into account. This is set to 20000 by +the TCP congestion mechanism into account. This is set to 4194304 by default, but can be changed using the \b network/TCP-gamma item. On linux, this value can be retrieved using the following @@ -373,15 +372,6 @@ can be set to 0 (disable this feature) or 1 (enable it). Note that with the default host model this option is activated by default. -\subsubsection options_model_network_sendergap Simulating sender gap - -(this configuration item is experimental and may change or disapear) - -It is possible to specify a timing gap between consecutive emission on -the same network card through the \b network/sender-gap item. This -is still under investigation as of writting, and the default value is -to wait 10 microseconds (1e-5 seconds) between emissions. - \subsubsection options_model_network_asyncsend Simulating asyncronous send (this configuration item is experimental and may change or disapear) @@ -485,13 +475,15 @@ For now, this configuration variable can take 2 values: \subsection options_modelchecking_visited model-check/visited, Cycle detection In order to detect cycles, the model-checker needs to check if a new explored -state is in fact the same state than a previous one. In order to do this, +state is in fact the same state than a previous one. For that, the model-checker can take a snapshot of each visited state: this snapshot is then used to compare it with subsequent states in the exploration graph. -The \b model-check/visited is the maximum number of states which are stored in -memory. If the maximum number of snapshotted state is reached some states will -be removed from the memory and some cycles might be missed. +The \b model-check/visited option is the maximum number of states which are stored in +memory. If the maximum number of snapshotted state is reached, some states will +be removed from the memory and some cycles might be missed. Small +values can lead to incorrect verifications, but large value can +exhaust your memory, so choose carefully. By default, no state is snapshotted and cycles cannot be detected. @@ -513,7 +505,7 @@ liveness violation) as well as the cycle for liveness properties. This dot file can then fed to the graphviz dot tool to generate an corresponding graphical representation. -\subsection options_modelchecking_max_depth model-check/max_depth, Depth limit +\subsection options_modelchecking_max_depth model-check/max-depth, Depth limit The \b model-checker/max-depth can set the maximum depth of the exploration graph of the model-checker. If this limit is reached, a logging message is @@ -1300,7 +1292,7 @@ when \b verbose-exit is set to 0 (it is to 1 by default). \subsection options_exception_cutpath Truncate local path from exception backtrace \verbatim ---cfg=exceptions/cutpath:1 +--cfg=exception/cutpath:1 \endverbatim This configuration option is used to remove the path from the