GNU/Linux man pages
Livre :
Expressions régulières,
Syntaxe et mise en oeuvre :
GNU/Linux |
RedHat 6.2(Zoot) |
|
 |
MPIL_Trace_on(2) |
 |
MPIL_Trace_on, MPIL_Trace_off − Start and stop LAM/MPI application tracing.
#include <net.h>
int
MPIL_Trace_on (void);
int MPIL_Trace_off (void);
subroutine
MPIL_TRACE_ON (ierr)
subroutine MPIL_TRACE_OFF (ierr)
integer ierr
These functions give the application the flexibility to generate traces only during certain interesting phases of the application’s execution. This technique can considerably reduce the size of the trace files and burden of displaying them.
Both functions are collective over MPI_COMM_WORLD. In typical usage, the -toff option of mpirun(1) would be used to enable tracing, but start with the runtime switch in the off position. At the beginning of an interesting phase of program execution, MPIL_Trace_on() would be called. MPIL_Trace_off() would be called after the interesting phase. Tracing can be turned on and off many times. Each period of tracing eventually forms a trace segment in the trace file extracted by lamtrace(1). If the on/off functions are never used and tracing is enabled with the -ton option of mpirun(1), a single trace segment is produced.
The on/off functions have no effect if tracing is not enabled by mpirun(1) with either -ton or -toff. Thus, an application can be littered with these functions but run without trace collection and very little additional overhead due to the no-operation function calls.
Limitations
After the volume of generated traces exceeds a preset limit,
the oldest traces are discarded in favour of new traces.
Avoiding discarded traces is further incentive to use
MPIL_Trace_on() and MPIL_Trace_off().
mpirun(1), lamtrace(1)
|
MPIL_Trace_on(2) | |