[mpiwg-rma] Single RMA synchronization for several window handles

Jim Dinan james.dinan at gmail.com
Sun Aug 10 10:48:02 CDT 2014


Hi Rolf,

I had initially proposed this in the context of passive target RMA.  Active
target RMA already notifies the receiver when data has arrived, but there
is no efficient way to get such a notification in passive target RMA.  I
think what you are proposing here would be syntactic sugar on top of the
existing interface --- could I implement this by fencing every window to
determine that all transfers are completed?

I agree with the comments regarding dynamic windows.  The merged window
would contain discontiguous buffers; thus, it would lose the ability to do
offset-based addressing and would need to use absolute (BOTTOM-based)
addressing.

 ~Jim.


On Fri, Aug 8, 2014 at 10:18 AM, Rolf Rabenseifner <rabenseifner at hlrs.de>
wrote:

> Jim,
>
> your topic "Reducing Synchronization Overhead Through Bundled
> Communication" may get also help if we would be able to
> combine several window handles to one superset window handle.
>
> If you have several windows for different buffers, but
> only one synchronization pattern, e.g. MPI_Win_fince
> then currently you must call MPI_Win_fence seperately
> for each window handle.
>
> I would propose:
>
> MPI_Win_combine (/*IN*/  int count,
>                  /*IN*/  MPI_Win *win,
>                  /*IN*/  MPI_Comm comm,
>                  /*OUT*/ MPI_Win *win_combined)
>
> The process group of comm must contain the process groups of all win.
> The resulting window handle win_combined can be used only
> in RMA synchronization calls and other helper routines,
> but not for dynamic window allocation nor for any
> RMA communication routine.
> Collective synchronization routines must be called by all processes
> of comm.
> The semantics of an RMA synchronization call using win_combined
> is defined as if the calls were seperately issued for
> each window handle of the array win. If group handles
> are part of the argument list of the synchronization call
> then the appropriate subset is used for each window handle in win.
>
> What do you think about this idea for MPI-4.0?
>
> Best regards
> Rolf
>
> ----- Original Message -----
> > From: "Jim Dinan" <james.dinan at gmail.com>
> > To: "MPI WG Remote Memory Access working group" <
> mpiwg-rma at lists.mpi-forum.org>
> > Sent: Thursday, August 7, 2014 4:08:32 PM
> > Subject: [mpiwg-rma] RMA Notification
> >
> >
> >
> > Hi All,
> >
> >
> > I have added a new proposal for an RMA notification extension:
> > https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/439
> >
> >
> > I would like to bring this forward for the RMA WG to consider as an
> > MPI-4 extension.
> >
> >
> > Cheers,
> >  ~Jim.
> > _______________________________________________
> > mpiwg-rma mailing list
> > mpiwg-rma at lists.mpi-forum.org
> > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-rma
>
> --
> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner at hlrs.de
> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530
> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832
> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner
> Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307)
> _______________________________________________
> mpiwg-rma mailing list
> mpiwg-rma at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-rma
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-rma/attachments/20140810/656934a6/attachment-0001.html>


More information about the mpiwg-rma mailing list