Comments

edited

Problem

To make fully nonblocking MPI libraries and codes, we want there to be available nonblocking constructors and destructors for communicators, windows, and files. This ticket separates out the request to add these functions in the RMA chapter. This only addresses constructors/destructors, not operations such as MPI_Win_fence.

Cross-correlates with Ticket #78 (Several chapters other than RMA and DPM) and #81 (DPM).

Proposal

Changes to the Text

Appropriate additional text is added to define and clarify the behavior of each new functions. Specific clarification on the usability of the handles before completion in the constructors will be made; specific clarification about the non-usability of the handles after calling the destructor will be made.

This comment has been minimized.

@wgropp : we did a preliminary reading in June; we did not, as you know, attempt a reading in Barcelona. There is full proposal text, but it needs review. What do you propose for December reading? I can re-read and tweak, but the RMA working group needs to weigh in.

This comment has been minimized.

On Sep 26, 2018, at 2:00 PM, William Gropp ***@***.***> wrote:
We’re setting things up on the RMA WG pages to make it easier to discuss and track issues. Probably the best thing is to start either start a new issue at https://github.com/mpiwg-rma/rma-issues/issues or on the WG wiki at https://github.com/mpiwg-rma/rma-issues/wiki/RMA-Working-Group-Wiki (it is currently hiding under the issues page but should be considered the RMA WG wiki, not the RMA issues wiki).
Bill
William Gropp
Director and Chief Scientist, NCSA
Thomas M. Siebel Chair in Computer Science
University of Illinois Urbana-Champaign
> On Sep 26, 2018, at 5:30 AM, Tony Skjellum ***@***.***> wrote:
>
> @wgropp <https://github.com/wgropp> : we did a preliminary reading in June; we did not, as you know, attempt a reading in Barcelona. There is full proposal text, but it needs review. What do you propose for December reading? I can re-read and tweak, but the RMA working group needs to weigh in.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANJTZvTOKctRTzXDAHQcBweeqUiFiAtGks5ue1dWgaJpZM4SYoeR>.
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

This comment has been minimized.

Good question. Perhaps there should be a separate working group that looked at global issues.
Bill
William Gropp
Director and Chief Scientist, NCSA
Thomas M. Siebel Chair in Computer Science
University of Illinois Urbana-Champaign

On Sep 26, 2018, at 2:08 PM, William Gropp ***@***.***> wrote:
Good question. Perhaps there should be a separate working group that looked at global issues.
Bill
William Gropp
Director and Chief Scientist, NCSA
Thomas M. Siebel Chair in Computer Science
University of Illinois Urbana-Champaign
> On Sep 26, 2018, at 7:05 AM, Tony Skjellum ***@***.***> wrote:
>
> Ok how do we correlate global issues with those ?
>
> Anthony Skjellum, PhD
> 205-807-4968
>
>
> > On Sep 26, 2018, at 2:00 PM, William Gropp ***@***.***> wrote:
> >
> > We’re setting things up on the RMA WG pages to make it easier to discuss and track issues. Probably the best thing is to start either start a new issue at https://github.com/mpiwg-rma/rma-issues/issues or on the WG wiki at https://github.com/mpiwg-rma/rma-issues/wiki/RMA-Working-Group-Wiki (it is currently hiding under the issues page but should be considered the RMA WG wiki, not the RMA issues wiki).
> >
> > Bill
> >
> > William Gropp
> > Director and Chief Scientist, NCSA
> > Thomas M. Siebel Chair in Computer Science
> > University of Illinois Urbana-Champaign
> >
> >
> >
> >
> >
> >
> > > On Sep 26, 2018, at 5:30 AM, Tony Skjellum ***@***.***> wrote:
> > >
> > > @wgropp <https://github.com/wgropp> : we did a preliminary reading in June; we did not, as you know, attempt a reading in Barcelona. There is full proposal text, but it needs review. What do you propose for December reading? I can re-read and tweak, but the RMA working group needs to weigh in.
> > >
> > > —
> > > You are receiving this because you were mentioned.
> > > Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANJTZvTOKctRTzXDAHQcBweeqUiFiAtGks5ue1dWgaJpZM4SYoeR>.
> > >
> >
> > —
> > You are receiving this because you were assigned.
> > Reply to this email directly, view it on GitHub, or mute the thread.
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANJTZlTCVm6hOW0qX4S4abomHPlRcR4Lks5ue22YgaJpZM4SYoeR>.
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

This comment has been minimized.

The instructions for issues at the forum site restricts those to ones ready for the full Forum to discuss - thus tickets/issues at the forum level are not appropriate for WG feedback. This is a reasonable position to take, as long as the WGs look at their issues (and I promise that RMA will be better :) ),
Bill
William Gropp
Director and Chief Scientist, NCSA
Thomas M. Siebel Chair in Computer Science
University of Illinois Urbana-Champaign

On Sep 26, 2018, at 7:15 AM, Tony Skjellum ***@***.***> wrote:
:-). I didn’t ever post issues on my WGs page ... we only do on the forum as tickets ... we’ve been assuming no one looks at WG issues
Anthony Skjellum, PhD
205-807-4968
> On Sep 26, 2018, at 2:08 PM, William Gropp ***@***.***> wrote:
>
> Good question. Perhaps there should be a separate working group that looked at global issues.
>
> Bill
>
> William Gropp
> Director and Chief Scientist, NCSA
> Thomas M. Siebel Chair in Computer Science
> University of Illinois Urbana-Champaign
>
>
>
>
>
>
> > On Sep 26, 2018, at 7:05 AM, Tony Skjellum ***@***.***> wrote:
> >
> > Ok how do we correlate global issues with those ?
> >
> > Anthony Skjellum, PhD
> > 205-807-4968
> >
> >
> > > On Sep 26, 2018, at 2:00 PM, William Gropp ***@***.***> wrote:
> > >
> > > We’re setting things up on the RMA WG pages to make it easier to discuss and track issues. Probably the best thing is to start either start a new issue at https://github.com/mpiwg-rma/rma-issues/issues or on the WG wiki at https://github.com/mpiwg-rma/rma-issues/wiki/RMA-Working-Group-Wiki (it is currently hiding under the issues page but should be considered the RMA WG wiki, not the RMA issues wiki).
> > >
> > > Bill
> > >
> > > William Gropp
> > > Director and Chief Scientist, NCSA
> > > Thomas M. Siebel Chair in Computer Science
> > > University of Illinois Urbana-Champaign
> > >
> > >
> > >
> > >
> > >
> > >
> > > > On Sep 26, 2018, at 5:30 AM, Tony Skjellum ***@***.***> wrote:
> > > >
> > > > @wgropp <https://github.com/wgropp> : we did a preliminary reading in June; we did not, as you know, attempt a reading in Barcelona. There is full proposal text, but it needs review. What do you propose for December reading? I can re-read and tweak, but the RMA working group needs to weigh in.
> > > >
> > > > —
> > > > You are receiving this because you were mentioned.
> > > > Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANJTZvTOKctRTzXDAHQcBweeqUiFiAtGks5ue1dWgaJpZM4SYoeR>.
> > > >
> > >
> > > —
> > > You are receiving this because you were assigned.
> > > Reply to this email directly, view it on GitHub, or mute the thread.
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANJTZlTCVm6hOW0qX4S4abomHPlRcR4Lks5ue22YgaJpZM4SYoeR>.
> >
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANJTZlaGw0z0GKq-pjrG0iv0pOj_6qN5ks5ue2_LgaJpZM4SYoeR>.

This comment has been minimized.

Global issues sounds like the remit of an ARB. We could choose to view the ARB as a special WG, i.e. needs 4 vote-eligible organisations to support its creation, gets its own Github fork (with a wiki, issues, and branches), discusses topics internally, brings Forum-ready proposals to plenary presentations - like any other WG. EPCC supports the creation of an "ARB" WG. We need +3 other vote-eligible organisations.

This comment has been minimized.

Also implicit, but worth making explicit, I am willing to offer my services as a member of such a group. Is this group freely accessible to all (like a normal WG) or by Forum-vote or at least by acclamation? The Forum should discuss decide at the next meeting.

This comment has been minimized.

I support having a discussion about developing a functioning ARB at the next Forum meeting.
Bill
William Gropp
Director and Chief Scientist, NCSA
Thomas M. Siebel Chair in Computer Science
University of Illinois Urbana-Champaign

This comment has been minimized.

On Sep 27, 2018, at 1:48 PM, William Gropp ***@***.***> wrote:
I support having a discussion about developing a functioning ARB at the next Forum meeting.
Bill
William Gropp
Director and Chief Scientist, NCSA
Thomas M. Siebel Chair in Computer Science
University of Illinois Urbana-Champaign
> On Sep 26, 2018, at 10:12 AM, Dan Holmes ***@***.***> wrote:
>
> Also implicit, but worth making explicit, I am willing to offer my services as a member of such a group. Is this group freely accessible to all (like a normal WG) or by Forum-vote or at least by acclamation? The Forum should discuss decide at the next meeting.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANJTZkyGensVmhLakOCHkANInKRJeDjnks5ue5lrgaJpZM4SYoeR>.
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.