Project

General

Profile

Feature #1818

Make AMPI's within-process messaging visible to Projections

Added by Sam White 7 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
AMPI
Target version:
-
Start date:
03/05/2018
Due date:
% Done:

0%


Description

Currently, AMPI does it's own messaging within a process. By that I mean AMPI invokes an entry method on the destination chare array element (AMPI rank), then once the message is matched it will do a direct memcpy() of the source buffer to the destination buffer, before invoking a Charm++ callback on the sender to notify it of completion of the send request. This means that only the rendezvous message and the completion message are visible in Projections, and all of the real message payload's transfer is invisible.

I'd like to add explicit tracing to AMPI to make the memcpy() visible in all Projections views and to have the number of bytes copied be visible in the appropriate views such as Communication over Time and Communication across PEs.

Also available in: Atom PDF