Hi Tony,
Apologies for not catching this sooner. There was no WG meeting today. We
moved to biweekly meetings because of reduced activity after the last spec
release. Our next meeting is supposed to be next Wednesday; however, it
lands on the Juneteenth holiday and I expect many folks from the US will be
off work. The next open meeting is July 17, but your topics might also fit
in well with Ryan's on July 3rd if you want to coordinate. Please let me
know when you'd like to cover these topics. Full meeting schedule is posted
here: https://urldefense.us/v3/__https://github.com/mpiwg-hybrid/hybrid-issues/wi…
Best,
~Jim.
On Wed, Jun 5, 2024 at 10:32 AM Skjellum, Anthony via mpiwg-hybridpm <
mpiwg-hybridpm(a)lists.mpi-forum.org> wrote:
> Jim, and others, I would like to discuss these topics (frozen proposals
> from MPI-4 and 4. 1) at the next meeting on June 12: Pbuf_prepare,
> Parrived_any I would like to see if we can get agreement on these and push
> into MPI-4. 2 or the next increment
> ZjQcmQRYFpfptBannerStart
> This Message Is From an External Sender
> This message came from outside your organization.
>
> ZjQcmQRYFpfptBannerEnd
> Jim, and others, I would like to discuss these topics (frozen proposals
> from MPI-4 and 4.1) at the next meeting on June 12:
>
> Pbuf_prepare, Parrived_any
>
> I would like to see if we can get agreement on these and push into MPI-4.2
> or the next increment after that, rather than MPI-5.
> I am sure this will take more than one discussion, since we didn't get
> these through before.
>
> Note: They are both marked for MPI-5 currently, presumably because we
> don't have a broad opening for MPI-4.2, and we haven't agreed on an MPI-4.3.
>
>
> Here are the tickets/issues:
>
> https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5…
> <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5…>
> (PR:https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pul…
> <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pull/7…> )
> – Ryan prepared the PR long ago.
>
> <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5…>
> MPI_Parrived_any API as an addition for Partititioned Communication ·
> Issue #537 · mpi-forum/mpi-issues
> <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5…>
> Problem The ability to take the next available partition is not supported
> in the current MPI-4.0 API. Proposal The API: MPI_Parrived_any(MPI_Request
> prequest, int *partition, int *flag); /* C inter...
> github.com
>
>
>
> https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/3…
> <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/3…>
> (with outdated PR: https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pull/2…
> <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pull/2…>
> ) – Ryan prepared the PR long ago.
>
>
> My apologies for long delays in follow up. We really need to resolve
> these issues as they impact both point-to-point partitioned and potential
> collective partitioned comms.
>
> I would encourage additional commentary on the issues; Patrick has made
> new, relevant observations about the dual roles of Pbuf_prepare recently on
> ticket#302, for example.
>
> Thank you all,
> Tony
>
> PS After that, I really do intend to hold a collective WG meeting to
> discuss partitioned collective ops 🙂 on June 19, or July 3 or 10, depending
> what works in tandem with the Hybrid calendar.
>
>
> Anthony Skjellum, PhD
> Professor of Computer Science
> Tennessee Technological University
> email: askjellum(a)tntech.edu
> cell: +1-205-807-4968
>
>
> _______________________________________________
> mpiwg-hybridpm mailing list
> mpiwg-hybridpm(a)lists.mpi-forum.org
> https://urldefense.us/v3/__https://lists.mpi-forum.org/mailman/listinfo/mpi…
>
Dan, it is good to hear from you. !!!!
Let's do a virtual coffee soon.
I am always interested in the multivendor solution---on that matter we should talk.
I do have staff (recent students) working on the experimental systems with various proposals for kernel and stream-triggered communication, for which we think Pbuf_prepare is of value to manage a) the unexpected message situation, b) forcing the initial matching. Patrick added some notes. We are all trying in the next year of our DOE center to advance concepts that we can try to put into the standard. They have to improve performance and predictability to make the cut, IMHO.
We have to make all these experimental systems work. We would like to see what Intel is offering along these lines.
We have a nearly complete survey paper to be shareable (sharable?) soon. It surveys eight API families for kernel and stream triggered, but Intel not represented in what we have studied as of now.
May we know the Intel approach to stream and or kernel triggered comms? Is it through the MPICH extensions we are studying?
We recognize that Parrived_any is a weaker requirement on the channel, allowing work to be processed as it arrives. Could also by handled with a wildcard in the Parrived.
Application programmerrs say this is what is reflective of the load-imbalanced arrival.
Australia is too far away for me too, and too expensive too. And seems like a bad venue to get people to go. I'd like to go there on a month's vacation someday, not for 4 days half-way around the globe or such.
I wish for help on the response to the Argonne progress for all paper, should you be at liberty to give opinions. If not allowable to be a co-author, I still would value guidance and input.
Quick response, hope coherent.
Tony
Anthony Skjellum, PhD
Professor of Computer Science
Tennessee Technological University
email: askjellum(a)tntech.edu
cell: +1-205-807-4968
________________________________
From: mpiwg-hybridpm <mpiwg-hybridpm-bounces(a)lists.mpi-forum.org> on behalf of Skjellum, Anthony via mpiwg-hybridpm <mpiwg-hybridpm(a)lists.mpi-forum.org>
Sent: Wednesday, June 5, 2024 9:31 AM
To: mpiwg-hybridpm(a)lists.mpi-forum.org <mpiwg-hybridpm(a)lists.mpi-forum.org>
Cc: Skjellum, Anthony <askjellum(a)tntech.edu>; Patrick Bridges <patrickb(a)unm.edu>; Ryan Eric Grant <reg1(a)queensu.ca>; Purushotham Bangalore <pvbangalore(a)ua.edu>
Subject: [mpiwg-hybridpm] Meeting for June 12, 2024
External Email Warning
This email originated from outside the university. Please use caution when opening attachments, clicking links, or responding to requests.
________________________________
Jim, and others, I would like to discuss these topics (frozen proposals from MPI-4 and 4. 1) at the next meeting on June 12: Pbuf_prepare, Parrived_any I would like to see if we can get agreement on these and push into MPI-4. 2 or the next increment
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Jim, and others, I would like to discuss these topics (frozen proposals from MPI-4 and 4.1) at the next meeting on June 12:
Pbuf_prepare, Parrived_any
I would like to see if we can get agreement on these and push into MPI-4.2 or the next increment after that, rather than MPI-5.
I am sure this will take more than one discussion, since we didn't get these through before.
Note: They are both marked for MPI-5 currently, presumably because we don't have a broad opening for MPI-4.2, and we haven't agreed on an MPI-4.3.
Here are the tickets/issues:
https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5… <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5…> (PR:https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pul… <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pull/7…> ) – Ryan prepared the PR long ago.
[https://urldefense.us/v3/__https://opengraph.githubassets.com/6ac106e7db39c… ]<https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5…>
MPI_Parrived_any API as an addition for Partititioned Communication · Issue #537 · mpi-forum/mpi-issues<https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5…>
Problem The ability to take the next available partition is not supported in the current MPI-4.0 API. Proposal The API: MPI_Parrived_any(MPI_Request prequest, int *partition, int *flag); /* C inter...
github.comhttps://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/3… <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/3…> (with outdated PR: https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pull/2… <https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pull/2…> ) – Ryan prepared the PR long ago.
My apologies for long delays in follow up. We really need to resolve these issues as they impact both point-to-point partitioned and potential collective partitioned comms.
I would encourage additional commentary on the issues; Patrick has made new, relevant observations about the dual roles of Pbuf_prepare recently on ticket#302, for example.
Thank you all,
Tony
PS After that, I really do intend to hold a collective WG meeting to discuss partitioned collective ops 🙂 on June 19, or July 3 or 10, depending
what works in tandem with the Hybrid calendar.
Anthony Skjellum, PhD
Professor of Computer Science
Tennessee Technological University
email: askjellum(a)tntech.edu
cell: +1-205-807-4968
Jim, and others, I would like to discuss these topics (frozen proposals from MPI-4 and 4.1) at the next meeting on June 12:
Pbuf_prepare, Parrived_any
I would like to see if we can get agreement on these and push into MPI-4.2 or the next increment after that, rather than MPI-5.
I am sure this will take more than one discussion, since we didn't get these through before.
Note: They are both marked for MPI-5 currently, presumably because we don't have a broad opening for MPI-4.2, and we haven't agreed on an MPI-4.3.
Here are the tickets/issues:
https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5… (PR:https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pul… ) – Ryan prepared the PR long ago.
[https://urldefense.us/v3/__https://opengraph.githubassets.com/6ac106e7db39c… ]<https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5… >
MPI_Parrived_any API as an addition for Partititioned Communication · Issue #537 · mpi-forum/mpi-issues<https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/5… >
Problem The ability to take the next available partition is not supported in the current MPI-4.0 API. Proposal The API: MPI_Parrived_any(MPI_Request prequest, int *partition, int *flag); /* C inter...
github.comhttps://urldefense.us/v3/__https://github.com/mpi-forum/mpi-issues/issues/3… (with outdated PR: https://urldefense.us/v3/__https://github.com/mpi-forum/mpi-standard/pull/2… ) – Ryan prepared the PR long ago.
My apologies for long delays in follow up. We really need to resolve these issues as they impact both point-to-point partitioned and potential collective partitioned comms.
I would encourage additional commentary on the issues; Patrick has made new, relevant observations about the dual roles of Pbuf_prepare recently on ticket#302, for example.
Thank you all,
Tony
PS After that, I really do intend to hold a collective WG meeting to discuss partitioned collective ops 🙂 on June 19, or July 3 or 10, depending
what works in tandem with the Hybrid calendar.
Anthony Skjellum, PhD
Professor of Computer Science
Tennessee Technological University
email: askjellum(a)tntech.edu
cell: +1-205-807-4968
Hi All,
We don't have an agenda, so today's meeting is canceled.
I did get responses for topics later this month and will put those on the
schedule soon. Please keep sending them.
Thanks,
~Jim.
Hi Folks,
We don't have topics for today (or any of the upcoming meetings). I hate to
keep holding this slot in your calendars and not use it. Please do respond
if there are topics that you're like to cover today or in the coming month.
Thanks,
~Jim.
On Tue, Jun 4, 2024 at 10:41 PM Jim Dinan <james.dinan(a)gmail.com> wrote:
> Hi All,
>
> Please send topics you'd like to cover at this Wednesday's meeting.
>
> Upcoming meeting dates for the summer are posted, please let me know if
> you have a topic that you'd like to schedule for any of the upcoming dates.
>
> https://urldefense.us/v3/__https://github.com/mpiwg-hybrid/hybrid-issues/wi…
>
> Best,
> ~Jim.
>
Hi All,
Please send topics you'd like to cover at this Wednesday's meeting.
Upcoming meeting dates for the summer are posted, please let me know if you
have a topic that you'd like to schedule for any of the upcoming dates.
https://urldefense.us/v3/__https://github.com/mpiwg-hybrid/hybrid-issues/wi…
Best,
~Jim.
