<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>On 8/4/13 5:44 PM, "Pavan Balaji" <<a href="mailto:balaji@mcs.anl.gov">balaji@mcs.anl.gov</a>> wrote:</div>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div>On 08/04/2013 06:33 PM, Barrett, Brian W wrote:</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>I'm either parsing your first or second sentence incorrectly. Are you</div>
<div>saying that you're doing a get in which the initiator-side address is in</div>
<div>a window and that reading the data after it's arrived is a load and</div>
<div>therefore causes problems for separate? Or are you saying that you</div>
<div>believe that puts/gets which move memory within a window are considered</div>
<div>loads?</div>
</blockquote>
<div><br>
</div>
<div>I'm saying the first one, yes. I didn't understand what you mean by the </div>
<div>second one, so I can't say for sure, but I think my answer is yes for </div>
<div>that one as well.</div>
<div><br>
</div>
<div>For the second question, if I do a PUT from a local window memory to a </div>
<div>remote window memory, it is a load on the local window memory. This is </div>
<div>based on the MPI-3 standard page 436 lines 29-30 (though it says </div>
<div>MPI_SEND, I think it is valid for MPI_PUT as well).</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Ah, ok. I did not interpret that paragraph that way. Since one-sided operations are explicitly not called out as being incoherent, I interpreted it as the one-sided operations must do the "right thing". But I can see your concern. Not sure what the
right solution is: 1) fix the specification of separate to do the right thing for one-sided operations 2) loosen the unified specification to work in more places, or 3) add a third memory model. 1) has some non-cache coherent issues in my mind. 2) means
we lose SHMEM-like semantics on those platforms, which greatly worries me. 3) might be the best option (ugh).</div>
<div><br>
</div>
<div>Brian</div>
<div>
<div>
<div><br>
</div>
<div>
<div>
<div style="font-family: Tahoma; font-size: 13px; "><font size="2" face="Tahoma">--</font></div>
<div style="font-family: Tahoma; font-size: 13px; "><font size="2" face="tahoma"> Brian W. Barrett</font></div>
<div style="font-family: Tahoma; font-size: 13px; "><font size="2" face="tahoma"> Scalable System Software Group</font></div>
<div style="font-family: Tahoma; font-size: 13px; "><font size="2" face="tahoma"> Sandia National Laboratories</font></div>
</div>
</div>
</div>
</div>
</body>
</html>