<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi All,<br>
<br>
After the comments on and off list about the shared file pointer
operations, and specifically about when the shared file pointer will
be updated, I'm finding it more compelling now to actually maintain
the order in which the shared file pointer is updated. This will
make the nonblocking collective and independent shared file pointer
operations non local, but in theory, as Edgar pointed out to me, all
shared file pointer operations can be non local anyhow. <br>
<br>
So I took out the Advice to Users that mentions that mixing
collective and independent operations is undefined, and added this
to the consistency semantics section for nonblocking collective I/O
operations:<br>
<br>
All nonblocking collective I/O calls are local and return
immediately, irrespective of the status of other<br>
processes. <font color="#cc0000">The shared file pointer operations
are an exception, because updating the shared file pointer might
be a non local operation.</font><br>
<br>
I guess this would be the "right" thing to do, and the original
intent for the split collective routines as Adam pointed out,
despite the contradiction in the standard.<br>
<br>
The updated draft is attached to the ticket url
<a class="moz-txt-link-freetext" href="https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/273">https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/273</a><br>
<br>
Thanks,<br>
Mohamad<br>
<br>
On 02/15/2012 05:39 PM, Quincey Koziol wrote:
<blockquote
cite="mid:5267B75F-A017-4818-ABEC-5C6DE9AB8CE2@hdfgroup.org"
type="cite">Hi Mohamad,
<div><span class="Apple-tab-span" style="white-space:pre"> </span>One
small comment about the change to lines 38-43 on p484: this
sentence: "All processes, belonging to the group of the
communicator that was used to open the file, must call
collective I/O operations (blocking and nonblocking) in the same
order." doesn't need any commas. Also, I would probably add the
same advise to users for MPI_FILE_IWRITE_ORDERED as you added
for MPI_FILE_IREAD_ORDERED.</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>Otherwise,
looks good to me, :-)</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>Quincey<br>
<div><br>
<div>
<div>On Feb 15, 2012, at 2:37 PM, Mohamad Chaarawi wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div text="#000000" bgcolor="#FFFFFF"> Hi All,<br>
<br>
I attached to the ticket (<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/273">https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/273</a>)
the updated draft with the suggested ticket 0 changes
from the reading at the last meeting.<br>
<br>
For your convenience, here are the changes made to the
text including the page number:<br>
<ul>
<li>
<pre wrap="">p:444 We should make table 13.1 have three rows: blocking, nonblocking & split collective, along with marking the split collectives as deprecated in the table (if possible). (ticket 0)
</pre>
</li>
<li>
<pre wrap="">p:451 (line 21), 456 (line 40), 463 (line 21) We need to change the 'void *' buffer parameters for the "write" routines to be 'const void *'.</pre>
</li>
<li>
<pre wrap="">p: 484 (line 46) "Quality" should be "High Quality".</pre>
</li>
<li>
<pre wrap="">p: 484 (line 38-43) The sentence ending with "in between" needs editing to indicate what the collective operations are "between".
</pre>
</li>
<ul>
<li>I rephrased this sentence a little and added a
reference to the collective semantics.<br>
</li>
</ul>
<li>
<pre wrap="">p: 484 (line 36) "belonging to the communicator" should be "belonging to the group of the communicator".</pre>
</li>
<li>
<pre wrap="">p: 484 (line 48) "All calls" should be changed to "All nonblocking collective I/O calls".</pre>
</li>
<li>
<pre wrap="">p: 445 (line 25) The sentence "In a nonblocking or split collective operation, the pointer is updated by the call that initiates the I/O, possibly before the access completes." should have a note about the split collectives being deprecated.</pre>
</li>
<li>
<pre>p"462 (line 28) Add advice to users to indicate the result of intermixing nonblocking collective and independent shared file pointer operations is undefined</pre>
</li>
</ul>
Please let me know if you have any comments about the
changes.<br>
<br>
Thanks,<br>
Mohamad<br>
<br>
</div>
_______________________________________________<br>
MPI3-IO mailing list<br>
<a moz-do-not-send="true"
href="mailto:MPI3-IO@lists.mpi-forum.org">MPI3-IO@lists.mpi-forum.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-io">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-io</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
MPI3-IO mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MPI3-IO@lists.mpi-forum.org">MPI3-IO@lists.mpi-forum.org</a>
<a class="moz-txt-link-freetext" href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-io">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-io</a>
</pre>
</blockquote>
<br>
</body>
</html>