From: Wolfgang Bangerth Date: Wed, 25 Sep 2002 18:03:43 +0000 (+0000) Subject: Clarify docs. X-Git-Tag: v8.0.0~17468 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=037d5d026f4d9cf292326a017b2589f791ff7ec9;p=dealii.git Clarify docs. git-svn-id: https://svn.dealii.org/trunk@6517 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/lac/include/lac/sparse_direct.h b/deal.II/lac/include/lac/sparse_direct.h index d995aeb506..7f6a2b1229 100644 --- a/deal.II/lac/include/lac/sparse_direct.h +++ b/deal.II/lac/include/lac/sparse_direct.h @@ -126,13 +126,16 @@ * * As an alternative, you can call the function @p{set_detached_mode} * right after calling the constructor. This lets the program fork, so - * that we now have two programs that communicate via pipes. Now - * everytime you call one of the functions of this class, it relays - * the data to the other program and lets it execute the respective - * function. The results are then transfered back. Since the MA27 - * functions are only called in the detached program, they will now no - * longer interfere with the respective calls to other functions with - * different data, so no synchronisation is necessary any more. + * that we now have two programs that communicate via pipes. The + * forked copy of the program then actually replaces itself by a + * program called @p{detached_ma27}, that is started in its place + * through the @p{execv} system call. Now everytime you call one of + * the functions of this class, it relays the data to the other + * program and lets it execute the respective function. The results + * are then transfered back. Since the MA27 functions are only called + * in the detached program, they will now no longer interfere with the + * respective calls to other functions with different data, so no + * synchronisation is necessary any more. * * The advantage of this approach is that as many instances of this * class may be active at any time as you want. This is handy, if your