1 /** \addtogroup SURF_API
3 \section SURF_doc Surf documentation
4 Surf is composed several components:
10 - \ref SURF_cpu_interface
11 - \ref SURF_network_interface
12 - \ref SURF_storage_interface
13 - \ref SURF_host_interface
14 - \ref SURF_vm_interface
22 /** \defgroup SURF_models Simulation Models
24 \brief Functions to declare the kind of models that you want to use
27 /** \defgroup SURF_simulation Simulation
29 \brief Functions for creating the environment and launching the simulation
31 This section describes the functions for initializing SURF, performing
32 the simulation and exiting SURF.
35 /** \defgroup SURF_build_api Create a new API
37 \brief How to build a new API on top of SURF
39 SURF provides the functionalities to simulate the platform. There are two main data types in SURF:
40 the actions and the resources. Several types of resources exist:
42 - the network resource,
46 The implementation of these resources depends on the platform
47 models you choose. You can select your model by calling
48 #surf_host_model_init_current_default() (which will give you a
49 CLM03 model), or similar (see \ref SURF_models).
51 To initialize SURF, call #surf_init(). Then
52 #surf_host_model_init_current_default() or #surf_host_model_init_ptask_L07()
53 to create the platform.
55 Then you can access the hosts with the global variables \ref host_list.
56 Some functions of the \ref SURF_host_interface and similar can give
57 you some information about:
58 - a host: get_speed(), get_available_speed();
59 - a network link: get_link_name(), get_link_latency(), get_link_bandwith();
60 - a route: get_route(), get_route_size().
62 During the simulation, call \a surf_host_model->execute() to schedule a
63 computation task on a host, or \a surf_host_model->communicate()
64 to schedule a communication task between two hosts. You can also create parallel task
65 with \a surf_host_model->extension_public->execute_parallel_task(). These functions return
66 a new action that represents the task you have just created.
68 To execute the actions created with \a execute(), \a communicate() or \a execute_parallel_task(), call
69 surf_solve(). The function surf_solve() is where the simulation takes place. It returns the
70 time elapsed to execute the actions. You can know what actions have changed their state thanks
71 to the states sets. For example, if your want to know what actions are finished,
72 extract them from \a surf_host_model->common_public->states.done_action_set.
73 Depending on these results, you can schedule other tasks and call surf_solve() again.
75 When the simulation is over, just call surf_exit() to clean the memory.
77 Have a look at the implementation of \ref MSG_API "MSG" and \ref SD_API "Simdag" to see how these module
78 interact with SURF. But if you want to create a new API on top of SURF,
79 we strongly recommend you to contact us before anyway.
84 @defgroup SURF_c_bindings SURF C bindings
86 @brief Describes the c bindings of SURF
90 @defgroup SURF_interface SURF Interface
92 @brief Describes the general interface for all components (Cpu, Network, Storage, Host, VM)
96 @defgroup SURF_cpu_interface SURF Cpu Interface
98 @brief Describes the general Cpu interface for all Cpu implementations
102 @defgroup SURF_network_interface SURF Network Interface
104 @brief Describes the general Network interface for all Network implementations
108 @defgroup SURF_storage_interface SURF Storage Interface
110 @brief Describes the general interface for all Storage implementations
114 @defgroup SURF_host_interface SURF Host Interface
116 @brief Describes the general interface for all Host implementations
120 @defgroup SURF_vm_interface SURF VM Interface
122 @brief Describes the general interface for all VM implementations
126 @defgroup SURF_lmm SURF Linear MaxMin
128 @brief Describes how the linear MaxMin system work
132 @defgroup SURF_callbacks SURF callbacks
134 @brief Describes how to use the SURF callbacks
138 @defgroup plugin_energy Energy Plugin
140 @brief Describes how to use the energy plugin.