XBT_IMPORT_NO_EXPORT= \
XBT_PUBLIC_DATA=extern \
XBT_INLINE= \
- XBT_PRIVATE=
+ XBT_PRIVATE= \
+ XBT_ATTRIB_DEPRECATED_v321(m)= \
+ XBT_ATTRIB_DEPRECATED_v322(m)= \
+ XBT_ATTRIB_DEPRECATED_v323(m)=
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
# this tag can be used to specify a list of macro names that should be expanded.
Entity name | Description
--------------- | -----------
\ref pf_storage_entity_storage_type "storage_type" | Defines a template for a particular kind of storage (such as a hard-drive) and specifies important features of the storage, such as capacity, performance (read/write), contents, ... Different models of hard-drives use different storage_types (because the difference between an SSD and an HDD does matter), as they differ in some specifications (e.g., different sizes or read/write performance).
-\ref pf_storage_entity_storage "storage" | Defines an actual instance of a storage type (disk, RAM, ...); uses a ``storage_type`` template (see line above) so that you don't need to re-specify the same details over and over again.
+\ref pf_tag_storage "storage" | Defines an actual instance of a storage type (disk, RAM, ...); uses a ``storage_type`` template (see line above) so that you don't need to re-specify the same details over and over again.
\ref pf_tag_mount "mount" | Must be wrapped by a \ref pf_tag_host tag; declares which storage(s) this host has mounted and where (i.e., the mountpoint).
| Attribute | Mandatory | Values | Description |
| ----------- | ----------- | -------- | ------------- |
-| id | yes | string | Refers to a \ref pf_storage_entity_storage "<storage>" entity that will be mounted on that computer |
+| id | yes | string | Refers to a \ref pf_tag_storage "<storage>" entity that will be mounted on that computer |
| name | yes | string | Path/location to/of the logical reference (mount point) of this disk
This tag must be enclosed by a \ref pf_tag_host tag. It then specifies where the mountpoint of a given storage device (defined by the ``id`` attribute)
This example is quite interesting, as the same device, called "Disk2", is mounted by
two hosts at the same time! Note, however, that the host called ``alice`` is actually
-attached to this storage, as can be seen in the \ref pf_storage_entity_storage "<storage>"
+attached to this storage, as can be seen in the \ref pf_tag_storage "<storage>"
tag. This means that ``denise`` must access this storage through the network, but SimGrid automatically takes
care of that for you.
\endverbatim
An easy way to model this scenario is to setup and define the RAM via the
-\ref pf_storage_entity_storage "storage" and \ref pf_storage_entity_storage_type "storage type"
+\ref pf_tag_storage "storage" and \ref pf_storage_entity_storage_type "storage type"
entities and attach it to a remote dummy host; then, every host can have their own links
to this host (modelling for instance certain scenarios, such as PCIe ...)
/** \ingroup m_process_management
* \brief Return the location on which a process is running.
- * \param process a process (nullptr means the current one)
* \return the sg_host_t corresponding to the location on which \a process is running.
*/
XBT_PUBLIC sg_host_t sg_host_self();
* Change a user state previously declared by pushing the new value to the state.
*
* \param host The name of the host to be considered.
- * \param state The name of the state previously declared.
- * \param value The value to be pushed.
+ * \param state_name The name of the state previously declared.
+ * \param value_name The value to be pushed.
*
* \see TRACE_host_state_declare, TRACE_host_set_state, TRACE_host_pop_state, TRACE_host_reset_state
*/
* Change a user state previously declared by removing the last value of the state.
*
* \param host The name of the host to be considered.
- * \param state The name of the state to be popped.
+ * \param state_name The name of the state to be popped.
*
* \see TRACE_host_state_declare, TRACE_host_set_state, TRACE_host_push_state, TRACE_host_reset_state
*/
* be nullptr.
* It can be retrieved with the function \ref simcall_process_get_data.
* \param host where the new agent is executed.
- * \param kill_time time when the process is killed
* \param argc first argument passed to \a code
* \param argv second argument passed to \a code
* \param properties the properties of the process
- * \param auto_restart either it is autorestarting or not.
*/
smx_actor_t simcall_process_create(const char* name, xbt_main_func_t code, void* data, sg_host_t host, int argc,
char** argv, std::map<std::string, std::string>* properties)
* \param flops_amount Array (of size host_nb) of computation amount of hosts (in bytes)
* \param bytes_amount Array (of size host_nb * host_nb) representing the communication
* amount between each pair of hosts
- * \param amount the SURF action amount
* \param rate the SURF action rate
* \param timeout timeout
* \return A new SIMIX execution synchronization
* \brief Registers a function to handle a kind of action
*
* Registers a function to handle a kind of action
- * This table is then used by \ref xbt_replay_action_runner
+ * This table is then used by \ref simgrid::xbt::replay_runner
*
* The argument of the function is the line describing the action, fields separated by spaces.
*
