X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/9e68ca10e951fb61e944c99c7774b1e415ae9f6d..76fea4c43fcfd7965f48c3c04b4b0bfe5c5581a3:/doc/doxygen/inside_extending.doc diff --git a/doc/doxygen/inside_extending.doc b/doc/doxygen/inside_extending.doc index 6332d506d2..bf38712a8e 100644 --- a/doc/doxygen/inside_extending.doc +++ b/doc/doxygen/inside_extending.doc @@ -1,10 +1,10 @@ -/*! -\page inside_extending Extending SimGrid +/*! +\page inside_extending Extending SimGrid We start to put TAGS in simgrid source code for having tutorials to see where is the important parts ans steps to create: -\li a new MSG functions or a new API. -\li a new model in surf. -\li new tags in xml files +\li \ref simgrid_dev_guide_api +\li \ref simgrid_dev_guide_model +\li \ref simgrid_dev_guide_tag \section simgrid_dev_guide_api How to add a new MSG function? Search for expression \"TUTORIAL: New API\". @@ -26,18 +26,168 @@ user@caraja:~/workspace/simgrid/src$ cg "TUTORIAL: New API" \endverbatim \section simgrid_dev_guide_model How to add a new model in surf? -Search for expression \"TUTORIAL: New model\". -\verbatim -user@caraja:~/workspace/simgrid/src$ cg "TUTORIAL: New model" -0 surf/new_model_private.h 2 /* TUTORIAL: New model -1 surf/surf.c 213 /* TUTORIAL: New model*/ -2 surf/surf_config.c 380 /* TUTORIAL: New model*/ -3 surf/surf_config.c 746 /* TUTORIAL: New model*/ -4 surf/new_model.c 8 /* TUTORIAL: New model*/ -5 include/surf/surf.h 157 /* TUTORIAL: New model*/ -6 include/surf/surf.h 345 /* TUTORIAL: New model*/ -7 include/surf/surf.h 661 /* TUTORIAL: New model*/ -\endverbatim +The figure below show the architecture of the SURF layer. This layer is composed +of different kind of models representing the differents systems we want to +modelize (i.e.cpu, network, storage, workstation, virtual machine). + +A model in simgrid is composed of three classes: Model, Resource and Action +(surf_interface.hpp). + +\image html surf++.png +\image latex surf++.pdf "surf++" width=\textwidth + +Actually there are five kind of models: CpuModel, NetworkModel, WorkstationModel, +WorkstationVMModel and StorageModel. For each kind of model, there is an +interface (e.g.: cpu_interface.hpp) and some implementations (e.g.: cpu_cas01.hpp, +cpu_ti.hpp). + +init function: +void surf_cpu_model_init_Cas01() +s_surf_model_description_t surf_network_model_description[] = { + +\subsection simgrid_dev_guide_model_implem How to add a new model implementation in surf? + +If you want to create a new implementation of a kind of model you must extend +the classes of the corresponding interfaces. + +For instance, if you want to add a new cup model called `Plop`, create two files +cpu_plop.hpp and cpu_plop_cpp which contains classes CpuPlopModel, CpuPlop and +CpuPlopAction implementating respectively the interfaces CpuModel, Cpu and +CpuAction. You also need to define a initializing function like this: + +~~~~ +void surf_cpu_model_init_plop() +{ + xbt_assert(!surf_cpu_model_pm); + + surf_cpu_model_pm = new CpuPlopModel(); + + sg_platf_host_add_cb(cpu_parse_init); + sg_platf_postparse_add_cb(cpu_add_traces); + + xbt_dynar_push(model_list, &surf_cpu_model_pm); +} +~~~~ + +and add an entry in the corresponding array in surf_interface.cpp + +~~~~ +s_surf_model_description_t surf_cpu_model_description[] = { + {"Cas01", + "Simplistic CPU model (time=size/power).", + surf_cpu_model_init_Cas01}, + {"Plop", + "The new plop CPU model.", + surf_cpu_model_init_plop}, + {NULL, NULL, NULL} /* this array must be NULL terminated */ +}; +~~~~ + +\subsection simgrid_dev_guide_model_kind How to add a new kind of model in surf? + +If you want to create a new kind of model, you must create a new interface +where you extend the classes Model, Resource and Action, and then create an +implementation of this interface. + + +\section simgrid_dev_guide_surf_callbacks How to use surf callbacks? + +Adding features to surf could also be handle by using surf callbacks (instead +of adding new implementation model). The list of available callbacks is +accessible there \ref SURF_callbacks. An example of using surf callbacks is the +energy plugin. If you want to add a plugin you need to define callback function +and to connect them to callbacks handler in an initialization function. + +~~~~ +static void MyNetworkLinkCreatedCallback(NetworkLinkPtr cpu){ + // your code +} + +static void MyNetworkLinkDestructedCallback(NetworkLinkPtr cpu){ + // your code +} + +static void MyNetworkCommunicationCallback(NetworkActionPtr cpu, + RoutingEdgePtr src, + RoutingEdgePtr dst){ + // your code +} + +void sg_my_network_plugin_init() { + surf_callback_connect(networkLinkCreatedCallbacks, + MyNetworkLinkCreatedCallback); + surf_callback_connect(networkLinkDestructedCallbacks, + MyNetworkLinkDestructedCallback); + surf_callback_connect(networkCommunicationCallbacks, + MyNetworkCommunicationCallback); +} +~~~~ + +Then you need to add an entry in surf_interface.cpp refering to your +initialization function. + +~~~~ +s_surf_model_description_t surf_plugin_description[] = { + {"Energy", + "Cpu energy consumption.", + sg_energy_plugin_init}, + {"MyNetworkPlugin", + "My network plugin.", + sg_my_network_plugin_init}, + {NULL, NULL, NULL} /* this array must be NULL terminated */ +}; +~~~~ + +\section simgrid_dev_guide_simcall How to add a new simcall? +A simcall is used to go from user mode to kernel mode. The workflow of +a simcall is the following: + +- ` simcall_()` + - `simcall_BODY_()` + - create the simcall + - `SIMIX_process_yield` if not maestro + - ========== KERNEL MODE ========== + - `SIMIX_simcall_pre` + - `SIMIX_pre_(simcall, )` + - `SIMIX_simcall_answer(simcall)` + +To simplify the simcall creation, we have made a python script that +generate most of the code and give helpers for the remaining stuff. +The script generating the simcalls (src/simix/simcalls.in) take in input +the src/simix/simcalls.in file where the simcalls are defined and generate +the following files: + +- simcall_generated_args_getter_setter.h: + functions to get and set simcall arguments +- simcall_generated_res_getter_setter.h: + functions to get and set simcall result +- simcall_generated_body.c: + the BODY function of the simcall +- simcall_generated_case.c: + the case of the SIMIX_simcall_pre function +- simcall_generated_enum.h: + the enum of simcalls +- simcall_generated_string.c: + string corresponding to the enum to debug + +Furthermode if the simcall_ or the SIMIX_pre_ function are missing, +a warning will show up with a prototype of the corresponding fonction to fill. + +The simcall.in file list all the simcalls in sections. A line starting by "##" +define a new section which will be replace by a "ifdef" in the generated code. +There is a simcall by line which follow this format: + +~~~~ +Simcall -> Name HasAnswer Res Args +Name -> [a-z0-9_]+ +Has_Answer -> "True" | "False" +Res -> "(" Type MaybeCast ")" +Args -> Args Arg | Arg +Arg -> "(" Name "," Type MaybeCast ")" +Type -> "char" | "const char*" | "int" | "long" | "unsigned char" | "unsigned short" | "unsigned int" | "unsigned long" | "float" | "double" | "void*" | "FPtr" | "const void*" | "size_t" | "sg_size_t" | "void" | "void*" +MaybeCast -> "," Cast | "" +Cast -> [a-z0-9_* ]+ +~~~~ \section simgrid_dev_guide_tag What is How to add a new tag for xml files? Search for expression \"TUTORIAL: New TAG\".