[Mpi3-ft] one sided

[Supalov, Alexander]

Thanks. Why not having two calls or modes of operation to cover both?

-----Original Message-----
From: mpi3-ft-bounces at lists.mpi-forum.org [mailto:mpi3-ft-bounces at lists.mpi-forum.org] On Behalf Of Darius Buntinas
Sent: Tuesday, October 18, 2011 9:57 PM
To: MPI 3.0 Fault Tolerance and Dynamic Process Control working Group
Subject: [Mpi3-ft] one sided


I got some feedback from Jim and Pavan on the one-sided section.  One thing Jim pointed out was that we don't want to make window creation synchronizing, and the fail-or-succeed everywhere requirement would do that.

If we say that window creation should not fail due to failed processes, that would accomplish the same thing:  If a window is created by a correct program, then it will succeed at all live processes.  Note that if an incorrect program specifies invalid parameters then the window creation may fail at some processes and succeed at others, but this is what we already have today.

However, it's possible that some implementations cannot satisfy this requirement because, e.g., they do collectives as part of the operation.  So maybe we should have two options:

  Either:
    window creation won't fail because if failed processes
  or
    window creation will either succeed or fail everywhere and if window creation fails at 
    any process it fails at every process

-d



_______________________________________________
mpi3-ft mailing list
mpi3-ft at lists.mpi-forum.org
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft
--------------------------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland 
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052