Re: information for profiling
Nathan E. Doss (doss@ERC.MsState.Edu)
Fri, 17 Nov 1995 18:20:23 -0600 (CST)
> I had to include several files to get access to the request data type.
> One reason was that I needed to find out the local communicator, so
> that I could then use this info to find out the processor id in
> the world communicator. The other reason that
> I needed access to request was to get the necessary information when
> the MPI_Start and MPI_Startall commands were used. I needed the
> following info for these calls: tag, partner, totallen, comm, and type.
> (eg. (*request)->chandle.tag, etc.)
One portable way to do this with the proposals that are currently on
the table is to use caching to store important information when the
request is created. Example:
MPI_Irecv_init ( ..., &request )
PMPI_Irecv_init ( ..., &request );
cache info on request
One drawback is that this may have more overhead than a profiling
library wants to pay. Especially when compared to accessing the
internal structure directly.
Nathan Doss doss@ERC.MsState.Edu