[trace] renaming almost all tracing files in src/instr details: - this is just an ongoing code re-organization - it serves as a preparation for jedule code in src/instr git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8959 48e7efb5-ca39-0410-a469-dd3cf9ba447f
graph of platform is always traced if tracing is enabled details: - tracing/platform:1 now only traces the categorized resource utilization git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8644 48e7efb5-ca39-0410-a469-dd3cf9ba447f
tracing: new configuration option to control if tracing is active or not details: - if tracing is 0, the tracing system is completely inactive even if SimGrid was compiled with tracing=on - by default it is 0 git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8617 48e7efb5-ca39-0410-a469-dd3cf9ba447f
two additional functions to declare categories (now with user colors) details: - TRACE_category_with_color (category, color) - TRACE_create_category_with_color (cat, type, parent_cat, color) - this function can be used to create hierarchical categories definition - color is a char* that must be in the following format "%f %f %f", red, green, blue where red, green, blue are float values in the interval [0, 1] - user can specify a NULL color, or simply call the TRACE_category (cat) or TRACE_create_category (cat, type, parent_cat) as before -> instrumentation will define random colors - but they might not be good colors for visu - no need to configure colors during visualization analysis git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8519 48e7efb5-ca39-0410-a469-dd3cf9ba447f
isolating uncategorized resource utilization tracing to get a cleaner trace git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8515 48e7efb5-ca39-0410-a469-dd3cf9ba447f
new configuration option tracing/smpi/group details: - by default, it is set to 0 - if is 0, the behavior of each MPI process (in the interface level: MPI_Send, Recv, ...) is not group by host (this means that you do not know where it was executed by looking only the trace) - otherwise, processes are grouped by host info: - traditional mpi-focused visualization tools usually do not group by hosts: that is the reason we are keeping the default value to 0 (not grouped) git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8498 48e7efb5-ca39-0410-a469-dd3cf9ba447f
moving TRACE_smpi_set_category to smpi_mpi.c so function can call smpi_bench_* details: - since smpi_bench_end generates a execute task, we have to call smpi_bench_end before changing the process's category - if we don't do so, we end up with a new category to an execute action that should have the process's old category - function prototype is kept in instr/instr.h git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8470 48e7efb5-ca39-0410-a469-dd3cf9ba447f
Indent include and src using this command: indent -kr -br -brs -ce -bbo --dont-break-procedure-type --no-tabs --cuddle-do-while --cuddle-else --indent-level2 --leave-preprocessor-space --no-space-after-function-call-names I also had to play with fromdos and to check that sg_unit_extractor.pl did not get fooled by XBT_TEST_UNIT lines splitted in half by indent. git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8394 48e7efb5-ca39-0410-a469-dd3cf9ba447f
tracing uncategorized resource utilization git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8384 48e7efb5-ca39-0410-a469-dd3cf9ba447f
cosmetics on tracing mechanism details: - no export of functions starting with __ or _ - functions ending with _alloc and _release are used to initialize tracing modules git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8361 48e7efb5-ca39-0410-a469-dd3cf9ba447f
registering the source and destination of all onelink routes git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8349 48e7efb5-ca39-0410-a469-dd3cf9ba447f
trace cosmetics details: - remove "__" from beginning of some functions name - making some functions static - moving a function to other file, making it static git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8321 48e7efb5-ca39-0410-a469-dd3cf9ba447f
trace: new interface function for tracing resource categorized utilization with SMPI details: - still experimental - include "instr/instr.h" in your code MPI - put TRACE_smpi_set_category ("name_of_your_cat") somewhere in the code that all processes execute. example: Do this: { ... TRACE_smpi_set_category (...); if (rank == 0){ }else{ } ... } instead of this: { ... if (rank == 0){ TRACE_smpi_set_category (...); }else{ } ... } - call TRACE_smpi_set_category (NULL) to de-activate the tracing of the platform utilization according to a category - all this only works if the smpi simulation is launched with the option --cfg=tracing/platform:1 (next commits will have an additional option in smpirun to handle that) git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8187 48e7efb5-ca39-0410-a469-dd3cf9ba447f
creating a source file dedicated to handle the categories git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8185 48e7efb5-ca39-0410-a469-dd3cf9ba447f
fullduplex support details: - added by Pedro - LV08 model accepts a new option 'fullduplex', enabling a more realistic TCP behavior - more details on the FAQ (that will be updated soon) git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8134 48e7efb5-ca39-0410-a469-dd3cf9ba447f
trace: functions to generate links, append a link type in the hierarchy of types git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8128 48e7efb5-ca39-0410-a469-dd3cf9ba447f
trace: a dictionary to keep link keys, put and get functions to manage it git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8127 48e7efb5-ca39-0410-a469-dd3cf9ba447f
tracing MPI collective operations implemented in SMPI details: - MPI Bcast, Barrier, Gather, Gather, Allgather, Reduce, Scan, Reduce_scatter, Alltoall and their 'v' variants - the tracing is only a state for now - the root rank is not used for now to identify which process is the root of operation (for those who have a root) - the trace is visualizable in Paje and Triva (SquarifiedTreemap) git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8125 48e7efb5-ca39-0410-a469-dd3cf9ba447f
tracing MPI_Init and MPI_Finalize (trace container creation and destruction) details: - added function to create the string that identifies a mpi_process container in the trace - processes are grouped by host git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8124 48e7efb5-ca39-0410-a469-dd3cf9ba447f
detecting if TRACE_start was called too soon (before TRACE_global_init) git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@8111 48e7efb5-ca39-0410-a469-dd3cf9ba447f