X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/c329ffaab94a1ec5eeb3f24a8da70790c79af923..54f9c8ad29f19e25c5966d6085f334941fc236c0:/doc/doxygen/options.doc diff --git a/doc/doxygen/options.doc b/doc/doxygen/options.doc index 98ebf9d78e..22cfa387c0 100644 --- a/doc/doxygen/options.doc +++ b/doc/doxygen/options.doc @@ -139,7 +139,8 @@ when using SimDag. - \b compound: Host model that is automatically chosen if you change the network and CPU models - \b ptask_L07: Host model somehow similar to Cas01+CM02 but - allowing parallel tasks + allowing "parallel tasks", that are intended to model the moldable + tasks of the grid scheduling literature. \subsection options_generic_plugin Plugins @@ -198,16 +199,10 @@ the \b maxmin/precision item (default value: 0.00001). Changing it may speedup the simulation by discarding very small actions, at the price of a reduced numerical precision. -\subsection options_model_nthreads Parallel threads for model updates +\subsection options_concurrency_limit Concurrency limit -By default, Surf computes the analytical models sequentially to share their -resources and update their actions. It is possible to run them in parallel, -using the \b surf/nthreads item (default value: 1). If you use a -negative or null value, the amount of available cores is automatically -detected and used instead. - -Depending on the workload of the models and their complexity, you may get a -speedup or a slowdown because of the synchronization costs of threads. +The maximum number of variables in a system can be tuned through +the \b maxmin/concurrency_limit item (default value: 100). Setting a higher value can lift some limitations, such as the number of concurrent processes running on a single host. \subsection options_model_network Configuring the Network model @@ -317,6 +312,15 @@ corresponding to the ns3::TcpL4Protocol::SocketType configuration item in NS3. The only valid values (enforced on the SimGrid side) are 'NewReno' or 'Reno' or 'Tahoe'. +\subsection options_model_storage Configuring the Storage model + +\subsubsection option_model_storage_maxfd Maximum amount of file descriptors per host + +Each host maintains a fixed-size array of its file descriptors. You +can change its size (1024 by default) through the \b +storage/max_file_descriptors item to either enlarge it if your +application requires it or to reduce it to save memory space. + \section options_modelchecking Configuring the Model-Checking To enable the SimGrid model-checking support the program should @@ -844,6 +848,30 @@ This is the default value: 1. http://simgrid.gforge.inria.fr/contrib/smpi-calibration-doc.html 2. http://simgrid.gforge.inria.fr/contrib/smpi-saturation-doc.html +\subsection options_smpi_papi_events smpi/papi-events: Trace hardware counters with PAPI + +\warning + This option is experimental and will be subject to change. + This feature currently requires superuser privileges, as registers are queried. + Only use this feature with code you trust! Call smpirun for instance via + smpirun -wrapper "sudo " + or run sudo sh -c "echo 0 > /proc/sys/kernel/perf_event_paranoid" + In the later case, sudo will not be required. + +\note + This option is only available when SimGrid was compiled with PAPI support. + +This option takes the names of PAPI counters and adds their respective values +to the trace files. (See Section \ref tracing_tracing_options.) + +It is planned to make this feature available on a per-process (or per-thread?) basis. +The first draft, however, just implements a "global" (i.e., for all processes) set +of counters, the "default" set. + +\verbatim +--cfg=smpi/papi-events:"default:PAPI_L3_LDM:PAPI_L2_LDM" +\endverbatim + \subsection options_smpi_global smpi/privatize-global-variables: Automatic privatization of global variables MPI executables are meant to be executed in separated processes, but SMPI is @@ -1058,13 +1086,12 @@ when \b verbose-exit is set to 0 (it is to 1 by default). --cfg=exceptions/cutpath:1 \endverbatim -This configuration option is an internal option and should normally not be used -by the user. It is used to remove the path from the backtrace -shown when an exception is thrown; if we didn't remove this part, the tests -testing the exception parts of simgrid would fail on most machines, as we are -currently comparing output. Clearly, the path used on different machines are almost -guaranteed to be different and hence, the output would -mismatch, causing the test to fail. +This configuration option is used to remove the path from the +backtrace shown when an exception is thrown. This is mainly useful for +the tests: the full file path makes the tests not reproducible, and +thus failing as we are currently comparing output. Clearly, the path +used on different machines are almost guaranteed to be different and +hence, the output would mismatch, causing the test to fail. \section options_log Logging Configuration @@ -1151,7 +1178,8 @@ silently overflow on other parts of the memory. - \c path: \ref options_generic_path - \c plugin: \ref options_generic_plugin -- \c surf/nthreads: \ref options_model_nthreads +- \c storage/max_file_descriptors: \ref option_model_storage_maxfd + - \c surf/precision: \ref options_model_precision - \c For collective operations of SMPI, please refer to Section \ref options_index_smpi_coll @@ -1168,6 +1196,7 @@ silently overflow on other parts of the memory. - \c smpi/ois: \ref options_model_smpi_ois - \c smpi/or: \ref options_model_smpi_or - \c smpi/os: \ref options_model_smpi_os +- \c smpi/papi-events: \ref options_smpi_papi_events - \c smpi/privatize-global-variables: \ref options_smpi_global - \c smpi/running-power: \ref options_smpi_bench - \c smpi/send-is-detached-thresh: \ref options_model_smpi_detached