[mpiwg-ft] FTWG Action Items

Wesley Bland wbland at mcs.anl.gov
Thu Dec 19 10:29:41 CST 2013

That’s what I was afraid of. AFAIK, both attributes and info keys aren’t really appropriate for this so the only way we could provide this information to the user is with a new API call: MPI_COMM_IS_REVOKED(). This wouldn’t be hard to add, but the question is whether it’s worth the trouble of adding it. The same thing could be accomplished with an MPI_SENDRECV to yourself, but that’s not really an elegant solution to put out there.

On Dec 19, 2013, at 10:16 AM, Jim Dinan <james.dinan at gmail.com> wrote:

> On Thu, Dec 19, 2013 at 11:06 AM, Wesley Bland <wbland at mcs.anl.gov> wrote:
> * Function to query the status of a communicator (is it revoked or not).
>         * If this were done via a communicator attribute, it would be the only one I’m aware of that provides information to the user that is set by the library. All others are stored by the user and retrieved by the user.
>         * Do we want to add a new API to take care of this, or can we confirm that it’s ok to do this via an attribute?
> Sorry, I guess I was thinking of RMA when I suggested this; I don't know if it's feasible to use communicator attributes in this way.  MPI_Win_get_attr() has several predefined keys for querying window properties, e.g. MPI_WIN_BASE, etc.  Described in section 11.2.6 in MPI 3.0.
>  ~Jim.
> _______________________________________________
> mpiwg-ft mailing list
> mpiwg-ft at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-ft/attachments/20131219/d7729320/attachment-0001.html>

More information about the mpiwg-ft mailing list