(surf)
- Bug fix in the lmm_solver.
(msg)
- - Interface to Paje (see http://www-id.imag.fr/Logiciels/paje/) through the function
- MSG_paje_output.
- - Introducing two new functions MSG_process_kill() and MSG_process_killall().
+ - New! Interface to Paje (see http://www-id.imag.fr/Logiciels/paje/)
+ through the function MSG_paje_output.
+ - New! Introducing two new functions MSG_process_kill() and MSG_process_killall().
- It is possible to bound the rate of a communication in MSG with
MSG_task_put_bounded() (was already in the previous version but I had forgotten
to write it in the changelog).
- Begin to move Gras examples to examples/gras/
- Let make distcheck work again (yeah!)
(documentation)
- - documentation overhault using doxygen.
+ - documentation overhauled using doxygen.
gtk-doc-tools is dead in SimGrid now.
- Automatically extract all existing logging categories, and add the list
to the documentation (long standing one, to say the less)
(gras)
- Cleanup the known architecture table. Reorder the entries to group what
- should be, and use a more consistant naming scheme.
+ should be, and use a more consistent naming scheme.
(some of the test dataset are still to be regenerated)
- New! Allow library to register globals on each process just as userdata
does.
Use it in msg and trp.
This cleans a lot the internals and helps enforcing privacy of the
headers between the gras components.
- - New! Add a timer mecanism, not unlike cron(8) and at(1).
+ - New! Add a timer mechanism, not unlike cron(8) and at(1).
- Bugfix: gras_os_time was delirious in RL.
- Bugfix: gras_trp_select/RL don't run into the wall when asked to select
onto 0 sockets.
- Reenable GRAS now that it works.
- --
+ -- Arnaud Legrand <Arnaud.Legrand@imag.fr> Mon, 14 Feb 2005 14:02:13 -0800
SimGrid (2.90) unstable; urgency=low
SimGrid now comprises 3 different projects : MSG, GRAS and SMPI.
I wanted to release the new MSG as soon as possible and I have
broken GRAS, which is the reason why, for now, only MSG is fully
- functionnal. A laconic description of these projects is available
+ functional. A laconic description of these projects is available
in the documentation.
* REVOLUTION 2: I have removed SG and I am now using a new simulation
Have a look in tools/platform_generation. There is a tiny script
that converts from the old platform format to the new one. Concerning
the application deployment format, parsing the old one is tricky.
- I think most of you should hower be able to convert your files. If
+ I think most of you should however be able to convert your files. If
it is really an issue, I can write a C code that does the conversion.
Let me know.
2) the toolbox tbx does not exist anymore. We now have a library
*****************************************************************************
* Follows the old GRAS changelog. It does not follow the same syntax, but I *
-* dont feel like converting the oldies. (Mt) *
+* don't feel like converting the oldies. (Mt) *
*****************************************************************************
2005-01-31 Arnaud
2004-11-28 Arnaud
- Main loop and datastructures of SURF. A cpu resource object is
- functionnal. Surf can thus be used to create cpu's with variable
+ functional. Surf can thus be used to create cpu's with variable
performance on which you can execute some actions.
2004-11-15 Martin Quinson
- Port to ARM. Simply added the alignment and size descriptions. Should
work, but the ARM machines are so slow that I didn't had the opportunity
- to 'make check' overthere yet.
+ to 'make check' over there yet.
2004-11-15 Arnaud Legrand
- Trace manager now written. It uses a heap structure and is therefore
- Rename every gras_* function that was in xbt/ to its xbt_
counterpart.
- Add a heap and a doubly-linked list to xbt
- - Added a dichotomy to the dictionnaries. make check works as well before
+ - Added a dichotomy to the dictionaries. make check works as well before
so I assume that the patch is correct. I do not know however if things
run effectively faster than before now. :)
- Introduction of the remote errors.
They are the result of a RMI/RPC on the remote machine.
ErrCodes being scalar values, you can't get the host on which those
- errors did happen. Extending the error mecanism as in Gnome is possible.
+ errors did happen. Extending the error mechanism as in Gnome is possible.
No idea yet whether it is a good idea.
2004-10-28 Martin Quinson
Note that the cycle detection is off by default since it impacts the
performance. Watch the data you feed GRAS with ;)
- This property is hereditary. Any element embeeded in a structure having it
+ This property is hereditary. Any element embedded in a structure having it
set have it set for the time of this data exchange.
You should set it both on sender and receiver side. If you don't set it on
It should allow to kill the last bits of gras first version soon.
- This is not completely satisfactory yet (dupplicate code with
- chunk_{send,recv}; a bit out of the plugin mecanism), but it should
+ This is not completely satisfactory yet (duplicate code with
+ chunk_{send,recv}; a bit out of the plugin mechanism), but it should
work.
- Simplify transport plugin (internal) interface by not passing any
- argument to _server and _client, but embeeding them in the socket
+ argument to _server and _client, but embedding them in the socket
struct directly.
2004-09-28 Martin Quinson
- Improvement to the remote testing toysuite
2004-07-10 Martin Quinson
- [autoconf mecanism]
+ [autoconf mechanism]
- get ride of a bunch of deprecated macros
- actually run the test for two-compliment, not only compile it :-/
- test whether the structures get packed (and bail out if yes. Damn.
2004-04-19 Martin Quinson
[Data description]
- - register init/exit functions within gras module mecanism
+ - register init/exit functions within gras module mechanism
- send/receive function.
Convertion is not implemented, but short-cutted if not needed.
struct/array elements are sent one by one (instead of block-wise), but
* implementation of the serveral programmation environment of the
* SimGrid toolkit (nammely, \ref MSG_API, \ref GRAS_API and \ref SMPI_API).
*
- * You should use those mecanism instead.
+ * You should use those mechanism instead.
*/
* -# basic operations
* -# Automatic parsing
* -# Simple manual definitions
- * -# Callback Persistant State: Simple push/pop mecanism
- * -# Callback Persistant State: Full featured mecanism
+ * -# Callback Persistant State: Simple push/pop mechanism
+ * -# Callback Persistant State: Full featured mechanism
*/
/*@{*/
* It specifies that the structure s_array contains two fields, and that the size of the array pointed
* by \a data is the \a length field, and that the \a father field is a simple reference.
*
- * If you cannot express your datadescs with this mecanism, you'll have to use the more advanced
+ * If you cannot express your datadescs with this mechanism, you'll have to use the more advanced
* (and somehow complex) one described below.
*
* \warning Since GRAS_DEFINE_TYPE is a macro, you shouldn't put any comma in your type definition
*
* If your types are dynamic, you'll need to add some extra callback. For example, there is a
* specific callback for the string type which is in charge of computing the length of the char
- * array. This is done with the cbps mecanism, explained in next section.
+ * array. This is done with the cbps mechanism, explained in next section.
*
* If your types may contain pointer cycle, you must specify it to GRAS using the @ref gras_datadesc_cycle_set.
*
/*@}*/
-/** @name 4. Callback Persistant State: Simple push/pop mecanism
+/** @name 4. Callback Persistant State: Simple push/pop mechanism
*
* Sometimes, one of the callbacks need to leave information for the next ones. If this is a simple integer (such as
* an array size), you can use the functions described here. If not, you'll have to play with the complete cbps interface.
/*@}*/
-/** @name 5. Callback Persistant State: Full featured mecanism
+/** @name 5. Callback Persistant State: Full featured mechanism
*
- * Sometimes, one of the callbacks need to leave information for the next ones. If the simple push/pop mecanism
+ * Sometimes, one of the callbacks need to leave information for the next ones. If the simple push/pop mechanism
* introduced in previous section isn't enough, you can always use this full featured one.
*/
* to add a version number to the message (by default, the version is set to 0). Any messages of the
* wrong version will be ignored by the applications not providing any specific callback for them.
*
- * This mecanism (stolen from the dynamic loader one) should ensure you to change the semantic of a given
+ * This mechanism (stolen from the dynamic loader one) should ensure you to change the semantic of a given
* message while still understanding the old one.
*/
/** @{ */
/* $Id$ */
-/* config - Dictionnary where the type of each cell is provided. */
+/* config - Dictionary where the type of each cell is provided. */
/* This is useful to build named structs, like option or property sets. */
* User modules and libraries can also use these facilities to handle
* their own configuration.
*
- * A configuration set contain several \e variables which have a uniq name
+ * A configuration set contain several \e variables which have a unique name
* in the set and can take a given type of value. For example, it may
* contain a \a size variable, accepting \e int values.
- * Moreover, of values.
*
* It is impossible to set a value to a variable which has not been registered before.
* Usually, the module registers all the options it accepts in the configuration set,
*
* To some extend, configuration sets can be seen as typed hash structures.
*
- * \todo This great mecanism is not used in SimGrid yet...
+ * \todo This great mechanism is not used in SimGrid yet...
*
- * \todo We need a callback mecanism so that the configurable code get
+ * \todo We need a callback mechanism so that the configurable code get
* notified of configuration changes.
*
* \section XBT_cfg_ex Example
/** @addtogroup XBT_error
*
- * This is how the errors get reported in the SimGrid toolkit. This mecanism is not
+ * This is how the errors get reported in the SimGrid toolkit. This mechanism is not
* as powerful as exceptions, but since we're using C, there is not much we can do.
*
* @{*/
}
void amok_base_exit(void) {
- /* No real module mecanism in GRAS so far, nothing to do. */
+ /* No real module mechanism in GRAS so far, nothing to do. */
}
* gras_datadesc_cycle_set:
*
* Tell GRAS that the pointers of the type described by ddt may present
- * some loop, and that the cycle detection mecanism is needed.
+ * some loop, and that the cycle detection mechanism is needed.
*
* Note that setting this option when not needed have a rather bad effect
* on the performance (several times slower on big data).
* gras_datadesc_cycle_unset:
*
* Tell GRAS that the pointers of the type described by ddt do not present
- * any loop and that cycle detection mecanism are not needed.
+ * any loop and that cycle detection mechanism are not needed.
* (default)
*/
void
* @param version: something like versionning symbol
* @param payload: datadescription of the payload
*
- * Registers a message to the GRAS mecanism. Use this version instead of
+ * Registers a message to the GRAS mechanism. Use this version instead of
* gras_msgtype_declare when you change the semantic or syntax of a message and
* want your programs to be able to deal with both versions. Internally, each
* will be handled as an independent message type, so you can register
-There is a plugin mecanism in here, and the selection is automatic
+There is a plugin mechanism in here, and the selection is automatic
If you open a socket in SG realm, you'll get a SG socket.
If you open a socket in RL realm, you'll get a TCP socket.
_gras_trp_plugins=xbt_dict_new();
#ifdef HAVE_WINSOCK2_H
- /* initialize the windows mecanism */
+ /* initialize the windows mechanism */
{
WORD wVersionRequested;
WSADATA wsaData;
/***
- *** Plugin mecanism
+ *** Plugin mechanism
***/
/* A plugin type */
* @arg cfg the config set
* @arg entry a string describing the element to register
*
- * The string may consist in several variable description separated by a space.
+ * The string may consist in several variable descriptions separated by a space.
* Each of them must use the following syntax: \<name\>:\<min nb\>_to_\<max nb\>_\<type\>
* with type being one of 'string','int', 'host' or 'double'.
*/
XBT_LOG_NEW_CATEGORY(xbt,"All XBT categories (simgrid toolbox)");
XBT_LOG_NEW_CATEGORY(surf,"All SURF categories");
XBT_LOG_NEW_CATEGORY(msg,"All MSG categories");
-XBT_LOG_NEW_DEFAULT_SUBCATEGORY(log,xbt,"Loggings from the logging mecanism itself");
+XBT_LOG_NEW_DEFAULT_SUBCATEGORY(log,xbt,"Loggings from the logging mechanism itself");
void xbt_log_init(int *argc,char **argv, const char *defaultlog) {
int i,j;
xbt_module_finalize_fct_t finalize;
};
-/** @brief Initialize the xbt mecanisms. */
+/** @brief Initialize the xbt mechanisms. */
void
xbt_init(int *argc, char **argv) {
xbt_init_defaultlog(argc, argv, NULL);
}
-/** @brief Initialize the xbt mecanisms. */
+/** @brief Initialize the xbt mechanisms. */
void
xbt_init_defaultlog(int *argc,char **argv, const char *defaultlog) {
static short int first_run = 1;
xbt_log_init(argc,argv,defaultlog);
}
-/** @brief Finalize the xbt mecanisms. */
+/** @brief Finalize the xbt mechanisms. */
void
xbt_exit(){
xbt_log_exit();
