<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I updated the draft and attached it to the ticket with Fab's
comments, which included moving the entire split collective section
to the deprecated chapter, and emphasizing more the progress rules.<br>
<br>
I would like to get some feedback especially on the nonblocking
Collective I/O section on page 484, which I updated to emphasize the
progress rules which wasn't very clear in the first draft.<br>
<br>
Right now it reads as:<br>
<br>
\subsection{Nonblocking Collective File Operations}<br>
%--------------------------------------  
;
<br>
\label{sec:io-semantics-nb-collective}<br>
Nonblocking collective file operations are subject to the same
restrictions as<br>
blocking collective I/O operations. All processes, belonging to the<br>
communicator that was used to open the file, must call collective
I/O<br>
operations (blocking and nonblocking) in the same order. In
particular, once a<br>
process calls a collective I/O operation, all other processes,
belonging to<br>
the communicator used to open the file, must eventually call the
same<br>
collective I/O operation, and no other collective I/O operation on
the same<br>
file handle in between.<br>
<br>
Nonblocking collective I/O operations do not match with blocking
collective<br>
I/O operations. Multiple nonblocking collective I/O operations can
be<br>
outstanding on a single file handle. Quality MPI implementations
should be<br>
able to support a large number of pending nonblocking I/O
operations.<br>
<br>
All calls are local and return immediately, irrespective of the
status of<br>
other processes. The call initiates the operation which may progress<br>
independently of any communication, computation, or I/O. The call
returns a<br>
request handle, which must be passed to a completion call. All input
arguments<br>
should not be modified, and all output buffers should not be
accessed before<br>
the completion call. The same progress rules described for
nonblocking<br>
collective operations apply for nonblocking collective I/O
operations. For a<br>
complete discussion, please refer to the semantics set forth in<br>
Section~\ref{sec:nbcoll} on page~\pageref{sec:nbcoll}.<br>
<br>
<br>
Thanks,<br>
Mohamad<br>
<br>
On 12/13/2011 04:49 PM, Mohamad Chaarawi wrote:
<blockquote cite="mid:4EE7D692.7040901@hdfgroup.org" type="cite">Hi
All,
<br>
<br>
I think enough people have joined to post to this list now..
<br>
Quincey will present ticket 273 (immediate non-blocking collective
I/O operations) for a first reading at the January meeting. I
attached an updated draft for IO chapter authors (or others) to
review before sending it out on the general mailing list.
<br>
Last time there was an issue with deprecating the split collective
routines. Let me know if you have any comments.
<br>
<br>
ticket url:
<br>
<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>
<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>