From: Christian Heinrich Date: Thu, 29 Oct 2015 14:28:48 +0000 (+0100) Subject: [Doc] Added description for the boost context factory X-Git-Tag: v3_13~1614^2~3 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/7ce752524bd815bb66b262e4288903c6a9ebfc93?hp=6a6c1a432ee6568c58d74d31746544e6afabdf6f [Doc] Added description for the boost context factory --- diff --git a/doc/doxygen/options.doc b/doc/doxygen/options.doc index 539c43ff4b..58c4af04b3 100644 --- a/doc/doxygen/options.doc +++ b/doc/doxygen/options.doc @@ -534,8 +534,8 @@ phase. \subsection options_virt_factory Selecting the virtualization factory -In SimGrid, the user code is virtualized in a specific mecanism -allowing the simulation kernel to control its execution: when a user +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. @@ -555,6 +555,10 @@ to the most effient: - \b raw: amazingly fast factory using a context switching mecanism of our own, directly implemented in assembly (only available for x86 and amd64 platforms for now) + - \b boost: This uses the [context implementation](http://www.boost.org/doc/libs/1_59_0/libs/context/doc/html/index.html) + of the boost library; you must have this library installed before + you compile SimGrid. (On Debian GNU/Linux based systems, this is + provided by the libboost-contexts-dev package.) The only reason to change this setting is when the debugging tools get fooled by the optimized context factories. Threads are the most