<!DOCTYPE html>
<!-- BaNnErBlUrFlE-BoDy-start -->
<!-- Preheader Text : BEGIN -->
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;height:0px;max-height:0px;opacity:0;overflow:hidden;">
Dear All, Here is a summary of today’s meeting using Zoom hub from the transcript. A number after each sentence can refer the part of the transcript, and it is very helpful. Regards, Shinji. RMA WG 2026-06-05 00: 00(GMT+9: 00) Key Outcomes The</div>
<!-- Preheader Text : END -->
<!-- Email Banner : BEGIN -->
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;opacity:0;overflow:hidden;">ZjQcmQRYFpfptBannerStart</div>
<!--[if ((ie)|(mso))]>
<table border="0" cellspacing="0" cellpadding="0" width="100%" style="padding: 16px 0px 16px 0px; direction: ltr" ><tr><td>
<table border="0" cellspacing="0" cellpadding="0" style="padding: 0px 10px 5px 6px; width: 100%; border-radius:4px; border-top:4px solid #90a4ae;background-color:#D0D8DC;"><tr><td valign="top">
<table align="left" border="0" cellspacing="0" cellpadding="0" style="padding: 4px 8px 4px 8px">
<tr><td style="color:#000000; font-family: 'Arial', sans-serif; font-weight:bold; font-size:14px; direction: ltr">
This Message Is From an External Sender
</td></tr>
<tr><td style="color:#000000; font-weight:normal; font-family: 'Arial', sans-serif; font-size:12px; direction: ltr">
This message came from outside your organization.
</td></tr>
</table>
</td></tr></table>
</td></tr></table>
<![endif]-->
<![if !((ie)|(mso))]>
<div dir="ltr" id="pfptBannerl2dxqy1" style="all: revert !important; display:block !important; text-align: left !important; margin:16px 0px 16px 0px !important; padding:8px 16px 8px 16px !important; border-radius: 4px !important; min-width: 200px !important; background-color: #D0D8DC !important; background-color: #D0D8DC; border-top: 4px solid #90a4ae !important; border-top: 4px solid #90a4ae;">
<div id="pfptBannerl2dxqy1" style="all: unset !important; float:left !important; display:block !important; margin: 0px 0px 1px 0px !important; max-width: 600px !important;">
<div id="pfptBannerl2dxqy1" style="all: unset !important; display:block !important; visibility: visible !important; background-color: #D0D8DC !important; color:#000000 !important; color:#000000; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-weight:bold !important; font-weight:bold; font-size:14px !important; line-height:18px !important; line-height:18px">
This Message Is From an External Sender
</div>
<div id="pfptBannerl2dxqy1" style="all: unset !important; display:block !important; visibility: visible !important; background-color: #D0D8DC !important; color:#000000 !important; color:#000000; font-weight:normal; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-size:12px !important; line-height:18px !important; line-height:18px; margin-top:2px !important;">
This message came from outside your organization.
</div>
</div>
<div style="clear: both !important; display: block !important; visibility: hidden !important; line-height: 0 !important; font-size: 0.01px !important; height: 0px"> </div>
</div>
<![endif]>
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;opacity:0;overflow:hidden;">ZjQcmQRYFpfptBannerEnd</div>
<!-- Email Banner : END -->
<!-- BaNnErBlUrFlE-BoDy-end -->
<html>
<head><!-- BaNnErBlUrFlE-HeAdEr-start -->
<style>
#pfptBannerl2dxqy1 { all: revert !important; display: block !important;
visibility: visible !important; opacity: 1 !important;
background-color: #D0D8DC !important;
max-width: none !important; max-height: none !important }
.pfptPrimaryButtonl2dxqy1:hover, .pfptPrimaryButtonl2dxqy1:focus {
background-color: #b4c1c7 !important; }
.pfptPrimaryButtonl2dxqy1:active {
background-color: #90a4ae !important; }
html:root, html:root>body { all: revert !important; display: block !important;
visibility: visible !important; opacity: 1 !important; }
</style>
<!-- BaNnErBlUrFlE-HeAdEr-end -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Dear All, </div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Here is a summary of today’s meeting
using Zoom hub from the transcript.</div>
<div class="moz-cite-prefix">A number after each sentence can refer
the part of the transcript, and it is very helpful.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Regards,<br>
Shinji. </div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">RMA WG 2026-06-05 00:00(GMT+9:00)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Key Outcomes</span></h2>
<div
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"
data-block-type="BLOCK_TYPE_PARAGRAPH"><span>The working group resolved critical threading and concurrency semantics for MPI device-side operations. </span><span
style="font-weight: 700;">Single-thread operation model adopted</span><span>: each MPI operation must be issued by a single thread, though multiple threads can issue different operations concurrently </span><cite
class="zm-citation-text">1</cite><cite class="zm-citation-text">2</cite><span>. </span><span
style="font-weight: 700;">Host-device epoch separation enforced</span><span>: concurrent operations from host and device within the same epoch are now explicitly erroneous, with flash operations also prohibited during concurrent device communication </span><cite
class="zm-citation-text">3</cite><cite class="zm-citation-text">4</cite><span>.</span></div>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;">
<span></span></h2>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Decisions Made</span></h2>
<ul style="margin-left:-18pt;">
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Threading model</span><span>: Only a single thread per working group is responsible for issuing each MPI operation; multiple threads may call MPI primitives concurrently to start multiple independent operations </span><cite
class="zm-citation-text">1</cite><cite class="zm-citation-text">2</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">No cooperative primitives</span><span>: Decided against introducing cooperative versions (like SHMEM/NCCL-style cooperative puts) in current proposal; may revisit as future extension </span><cite
class="zm-citation-text">1</cite><cite class="zm-citation-text">5</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Thread safety alignment</span><span>: Device operations always operate in MPI_THREAD_MULTIPLE mode without host-side thread model restrictions </span><cite
class="zm-citation-text">6</cite><cite class="zm-citation-text">7</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Epoch isolation</span><span>: It is erroneous to call communication procedures on the same window from both host and device within the same access epoch </span><cite
class="zm-citation-text">3</cite><cite class="zm-citation-text">8</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Flash semantics</span><span>: Device-side flush only flushes device-initiated operations; host-side flush must flush both host and device operations using reference counters or completion queue polling </span><cite
class="zm-citation-text">9</cite><cite class="zm-citation-text">10</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Concurrent flush prohibition</span><span>: Issuing flush operations on the host concurrent with communication operations on the device is erroneous </span><cite
class="zm-citation-text">4</cite></li>
</ul>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Technical Clarifications</span></h2>
<ul style="margin-left:-18pt;">
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Memory fence semantics</span><span>: WinSync should be defined as a memory fence (system fence) on the device, similar to host-side shared memory behavior </span><cite
class="zm-citation-text">11</cite><cite class="zm-citation-text">12</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Implementation flexibility</span><span>: Multiple concurrent puts from different threads may be inefficient depending on implementation (e.g., proxy through host vs. direct memcopy vs. NIC access) </span><cite
class="zm-citation-text">13</cite><cite class="zm-citation-text">14</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Race conditions</span><span>: Same race condition risks exist as on CPU when multiple threads call operations without proper synchronization </span><cite
class="zm-citation-text">15</cite><cite class="zm-citation-text">16</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Implementation overhead</span><span>: Host flush of device operations requires maintaining reference counters in global memory or polling device completion queues </span><cite
class="zm-citation-text">9</cite><cite class="zm-citation-text">10</cite></li>
</ul>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Removed Content</span></h2>
<ul style="margin-left:-18pt;">
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">"When configured correctly" sentence</span><span>: Removed as non-transparent and repetitive </span><cite
class="zm-citation-text">17</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Thread restriction paragraph</span><span>: Removed confusing paragraph about MPI thread model restrictions since device operations don't share synchronization with host </span><cite
class="zm-citation-text">6</cite><cite class="zm-citation-text">7</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">"As if by CPU thread" clause</span><span>: Removed since windows are now separate and don't share synchronization primitives between host and device </span><cite
class="zm-citation-text">6</cite><cite class="zm-citation-text">18</cite></li>
</ul>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Text Revisions</span></h2>
<ul style="margin-left:-18pt;">
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Communication operations bullet expanded to clarify multiple threads can call concurrently to start multiple independent operations </span><cite
class="zm-citation-text">19</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Erroneous condition reworded: "It is erroneous to call communication procedures on the same window from both host and device within the same epoch" </span><cite
class="zm-citation-text">3</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Added separate sentence: "It is erroneous to issue flush operations on the host concurrent with communication operations on a device" </span><cite
class="zm-citation-text">4</cite></li>
</ul>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Pending Confirmation</span></h2>
<ul style="margin-left:-18pt;">
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Implementation feasibility validation needed for host flush of device operations (reference counter overhead acceptable) </span><cite
class="zm-citation-text">9</cite><cite class="zm-citation-text">10</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Verification that no epoch manipulation primitives (lock/unlock) are exposed for GPU windows, only flush available </span><cite
class="zm-citation-text">20</cite></li>
</ul>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Other Updates</span></h2>
<ul style="margin-left:-18pt;">
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Notify proposal status</span><span>: First reading at forum went well with only minor changes needed; no significant opposition; proceeding to no-no vote </span><cite
class="zm-citation-text">21</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Transcript availability</span><span>: Joseph will record to cloud for automatic transcription going forward </span><cite
class="zm-citation-text">22</cite></li>
</ul>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Action Items</span></h2>
<ul style="margin-left:-18pt;">
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Joseph</span><span>: Review and implement minor changes from Notify proposal forum reading before next meeting </span><cite
class="zm-citation-text">21</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Alex</span><span>: Update proposal text with agreed threading model clarifications and remove identified confusing paragraphs </span><cite
class="zm-citation-text">2</cite><cite class="zm-citation-text">19</cite></li>
<li
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span
style="font-weight: 700;">Alex</span><span>: Add concurrent flush prohibition language to proposal </span><cite
class="zm-citation-text">4</cite></li>
</ul>
<h2
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"><span>Next Meeting</span></h2>
<div
style="white-space: pre-wrap; margin-top: 0; margin-bottom: 0;text-align: left;"
data-block-type="BLOCK_TYPE_PARAGRAPH"><span>Two weeks from current meeting date </span><cite
class="zm-citation-text">4</cite></div>
<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2026/06/04 木曜日 20:52, Joseph
Schuchart via mpiwg-rma wrote:<br>
</div>
<blockquote type="cite"
cite="mid:73d3ea43-fe8b-4c68-afb6-0757702aced3@stonybrook.edu">
<!-- BaNnErBlUrFlE-BoDy-start -->
<!-- Preheader Text : BEGIN -->
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div
style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;height:0px;max-height:0px;opacity:0;overflow:hidden;">
Dear all, We’ll meet again this week Thursday to continue the
discussion on device-side RMA and recap the Notified RMA reading
at the Forum meeting this week. As always, we’re meeting at 10am
US Central and the connection info is available at</div>
<!-- Preheader Text : END -->
<!-- Email Banner : BEGIN -->
<div
style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;opacity:0;overflow:hidden;">ZjQcmQRYFpfptBannerStart</div>
<!--[if ((ie)|(mso))]>
<table border="0" cellspacing="0" cellpadding="0" width="100%" style="padding: 16px 0px 16px 0px; direction: ltr" ><tr><td>
<table border="0" cellspacing="0" cellpadding="0" style="padding: 0px 10px 5px 6px; width: 100%; border-radius:4px; border-top:4px solid #90a4ae;background-color:#D0D8DC;"><tr><td valign="top">
<table align="left" border="0" cellspacing="0" cellpadding="0" style="padding: 4px 8px 4px 8px">
<tr><td style="color:#000000; font-family: 'Arial', sans-serif; font-weight:bold; font-size:14px; direction: ltr">
This Message Is From an External Sender
</td></tr>
<tr><td style="color:#000000; font-weight:normal; font-family: 'Arial', sans-serif; font-size:12px; direction: ltr">
This message came from outside your organization.
</td></tr>
</table>
</td></tr></table>
</td></tr></table>
<![endif]-->
<!--[if !((ie)|(mso))]-->
<div dir="ltr" id="pfptBannerqdukupv"
style="all: revert !important; display:block !important; text-align: left !important; margin:16px 0px 16px 0px !important; padding:8px 16px 8px 16px !important; border-radius: 4px !important; min-width: 200px !important; background-color: #D0D8DC !important; background-color: #D0D8DC; border-top: 4px solid #90a4ae !important; border-top: 4px solid #90a4ae;">
<div id="pfptBannerqdukupv"
style="all: unset !important; float:left !important; display:block !important; margin: 0px 0px 1px 0px !important; max-width: 600px !important;">
<div id="pfptBannerqdukupv"
style="all: unset !important; display:block !important; visibility: visible !important; background-color: #D0D8DC !important; color:#000000 !important; color:#000000; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-weight:bold !important; font-weight:bold; font-size:14px !important; line-height:18px !important; line-height:18px">
This Message Is From an External Sender </div>
<div id="pfptBannerqdukupv"
style="all: unset !important; display:block !important; visibility: visible !important; background-color: #D0D8DC !important; color:#000000 !important; color:#000000; font-weight:normal; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-size:12px !important; line-height:18px !important; line-height:18px; margin-top:2px !important;">
This message came from outside your organization. </div>
</div>
<div
style="clear: both !important; display: block !important; visibility: hidden !important; line-height: 0 !important; font-size: 0.01px !important; height: 0px"> </div>
</div>
<!--[endif]-->
<div
style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;max-height:0px;opacity:0;overflow:hidden;">ZjQcmQRYFpfptBannerEnd</div>
<!-- Email Banner : END -->
<!-- BaNnErBlUrFlE-BoDy-end -->
<!-- BaNnErBlUrFlE-HeAdEr-start -->
<style>#pfptBannerqdukupv { all: revert !important; display: block !important;
visibility: visible !important; opacity: 1 !important;
background-color: #D0D8DC !important;
max-width: none !important; max-height: none !important }.pfptPrimaryButtonqdukupv:hover, .pfptPrimaryButtonqdukupv:focus {
background-color: #b4c1c7 !important; }.pfptPrimaryButtonqdukupv:active {
background-color: #90a4ae !important; }html:root, html:root>body { all: revert !important; display: block !important;
visibility: visible !important; opacity: 1 !important; }</style>
<!-- BaNnErBlUrFlE-HeAdEr-end -->
<pre
style="font-family: sans-serif; font-size: 100%; white-space: pre-wrap; word-wrap: break-word">Dear all,
We’ll meet again this week Thursday to continue the discussion on
device-side RMA and recap the Notified RMA reading at the Forum meeting
this week.
As always, we’re meeting at 10am US Central and the connection info is
available at <a
href="https://urldefense.us/v3/__https://github.com/mpiwg-rma/mpi-standard/wiki__;!!G_uCfscf7eWS!flqYDljgFSfM8vKiCb_MmZ0qVDk1_fex7UtOxiJLwNnPQI6_p1NGrTs9h-lpDPSnDsJwb8O49naES5xk5xvM55x69ZC96pX_R8o40It0D-4$"
moz-do-not-send="true" class="moz-txt-link-freetext">https://urldefense.us/v3/__https://github.com/mpiwg-rma/mpi-standard/wiki__;!!G_uCfscf7eWS!flqYDljgFSfM8vKiCb_MmZ0qVDk1_fex7UtOxiJLwNnPQI6_p1NGrTs9h-lpDPSnDsJwb8O49naES5xk5xvM55x69ZC96pX_R8o40It0D-4$</a>.
Cheers
Joseph
​
</pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
mpiwg-rma mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpiwg-rma@lists.mpi-forum.org">mpiwg-rma@lists.mpi-forum.org</a>
<a class="moz-txt-link-freetext" href="https://urldefense.us/v3/__https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma__;!!G_uCfscf7eWS!bdXWUs2Xdbvu8jVF4hJqjLRWrwJ7bbPngH6LN2j4T6spDfKUyd0O-CHGi0LEYVWUkDchR4lkR5yuCPc6w_3ZBP9R9JM$">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>