Interesting idea. You could wrap mpi.h in another header.. say mympi.h and
inline or #define each mpi send call with a call which took it's instruction
pointer and prepended it to the message and added the requisite number of
bytes to the message before actually calling into MPI.
The profiling layer might achieve this for you, I'm not entirely sure if it
manifests itself as inline code or as actual code in the ELF's .text.
Anybody know?
Craig
On 8/3/06, Oleg Morajko <olegmorajko_at_[hidden]> wrote:
>
> Hi there,
>
> I am looking for a general solution that would allow for attaching extra
> informacion to every MPI message sent and access this data after receive. I
> mean a kind of out-out-bound (or urgent) data as in TCP/IP protocol. The
> goal is to track sender callpoint address in a receiver process in order to
> correlate sends and receives down to file/line in source code.
>
> The requirement is not to modify a MPI-based application source code, but
> rather modify MPI implementation (or create a kind-of wrapper for MPI calls)
> that could do that. It's enough to pass just one integer value (tag field
> cannot be used for that purpose). I'm using dynamic instrumentation
> (DynInst) and have the ability to introduce run-time modifications. The
> ideal solution would be the ability add some extra integer to message
> envelope (in a reserved field for example) but without recompiling the MPI
> implementation - so that 2 implementations (instrumented one and normal
> one) could cooperate without problems.
>
> Any ideas how to do that?
>
> Regards,
> --Oleg
>
> Aplicaciones en Informatica Avanzada S.A.
> c./Artesans 10, 08291 Cerdanyola del Valles,
> Barcelona, Spain
>
>
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
>
|
