From: Guillaume Serrière Date: Wed, 17 Apr 2013 15:31:19 +0000 (+0200) Subject: Correction of documentation. X-Git-Tag: v3_9_90~416 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/2e65689673b8bb15e19e8257f3be74283eed061d Correction of documentation. If 0 is set as context/nthreads configuration value, the amount of core will be also auto-calculated. Signed-off-by: Guillaume Serrière --- diff --git a/doc/doxygen/options.doc b/doc/doxygen/options.doc index 02f6728456..5f9a58ff93 100644 --- a/doc/doxygen/options.doc +++ b/doc/doxygen/options.doc @@ -173,7 +173,7 @@ price of a reduced numerical precision. 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 value, the amount of available cores is automatically +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 @@ -401,8 +401,8 @@ If you are using the \c ucontext or \c raw context factories, you can request to execute the user code in parallel. Several threads are launched, each of them handling as much user contexts at each run. To actiave this, set the \b contexts/nthreads item to the amount of -cores that you have in your computer (or -1 to have the amount of cores -auto-detected). +cores that you have in your computer (or lower than 1 to have +the amount of cores auto-detected). Even if you asked several worker threads using the previous option, you can request to start the parallel execution (and pay the