From 2481f6c44bc25a74776981f3fe332ab0ab1198c1 Mon Sep 17 00:00:00 2001 From: alegrand Date: Thu, 13 Jul 2006 23:30:57 +0000 Subject: [PATCH] Updating the SG/SimDAG section (again!). git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@2570 48e7efb5-ca39-0410-a469-dd3cf9ba447f --- doc/FAQ.doc | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/doc/FAQ.doc b/doc/FAQ.doc index 80c32cb52e..e353e180f6 100644 --- a/doc/FAQ.doc +++ b/doc/FAQ.doc @@ -534,12 +534,11 @@ patterns. Some old codes using SG are currently under rewrite using \subsection faq_SG_DAG How to implement a distributed dynamic scheduler of DAGs. Distributed is somehow "contagious". If you start making distributed -decisions, there is no way to handle DAGs directly anymore (unless I am -missing something). You have to encode your DAGs in term of communicating -process to make the whole scheduling process distributed. Believe me, it is -worth the effort since you'll then be able to try your algorithms in a very -wide variety of conditions. Here is an example of how you could do that. -Assume T1 has to be done before T2. +decisions, there is no way to handle DAGs directly anymore (unless I +am missing something). You have to encode your DAGs in term of +communicating process to make the whole scheduling process +distributed. Here is an example of how you could do that. Assume T1 +has to be done before T2. \verbatim int your_agent(int argc, char *argv[] { @@ -561,11 +560,8 @@ Assume T1 has to be done before T2. \endverbatim If you decide that the distributed part is not that much important and that -DAG is really the level of abstraction you want to work with (but it -prevents you from having "realistic" platform modeling), then you should -keep using the 2.18.5 versions until somebody has ported SG on top of SURF. -Note however that SURF will be slower than the old SG to handle traces with -a lots of variations (there is no trace integration anymore). +DAG is really the level of abstraction you want to work with, then you should +give a try to \ref SD_API. \section faq_dynamic Dynamic resources and platform building -- 2.20.1