From d55d91ed057b45ff15d00ea7d503132f7d174bac Mon Sep 17 00:00:00 2001 From: Martin Quinson Date: Wed, 7 Jun 2017 17:39:30 +0200 Subject: [PATCH] small doc improvement --- doc/doxygen/options.doc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/doxygen/options.doc b/doc/doxygen/options.doc index 6a94beb730..d8966600b4 100644 --- a/doc/doxygen/options.doc +++ b/doc/doxygen/options.doc @@ -544,7 +544,8 @@ In SimGrid, the user code is virtualized in a specific mechanism that allows the simulation kernel to control its execution: when a user process requires a blocking action (such as sending a message), it is interrupted, and only gets released when the simulated clock reaches -the point where the blocking operation is done. +the point where the blocking operation is done. This is explained +graphically in the [relevant tutorial, available online](http://simgrid.gforge.inria.fr/tutorials/simgrid-simix-101.pdf). In SimGrid, the containers in which user processes are virtualized are called contexts. Several context factory are provided, and you can @@ -553,7 +554,7 @@ configuration item. Some of the following may not exist on your machine because of portability issues. In any case, the default one should be the most effcient one (please report bugs if the auto-detection fails for you). They are approximately sorted here from -the slowest to the most effient: +the slowest to the most efficient: - \b thread: very slow factory using full featured threads (either pthreads or windows native threads). They are slow but very -- 2.20.1