I was able to make almost all of the changes that were suggested.
Changes since last week's release are marked with "General" change bars.
The major changes are listed below; I did not include a list of
typos and minor corrections. If your favorite change did not make
it into this draft, there's always the January draft...
Thanks to everyone involved, I think the chapter looks very solid
for the Supercomuting release. Special thanks go to Albert Cheng,
Richard Frost, Leslie Hart, Steve Huss-Lederman, Terry Jones,
John May, Tyce McLarty, Jean-Pierre Prost, Ian Stockdale, David Taylor,
and Rajeev Thakur for sending many useful comments (too many :-).
- bill
Bill Nitzberg nitzberg@nas.nasa.gov
NAS Parallel Systems, MRJ, Inc.
NASA Ames Research Center, M/S 258-6 Tel: (415) 604-4513
Moffett Field, CA 94035-1000 FAX: (415) 966-8669
----------
Routine names have been changed to MPI_<object>_<action>_<subset>:
MPI_FILE_GET_COMM
MPI_FILE_GET_AMODE
MPI_FILE_SET_INFO
MPI_FILE_GET_INFO
MPI_FILE_GET_SIZE
MPI_FILE_SET_VIEW
MPI_FILE_GET_VIEW
MPI_FILE_GET_POSITION
MPI_FILE_GET_POSITION_SHARED
MPI_FILE_GET_TYPE_SIZE
MPI_FILE_GET_TYPE_EXTENT
MPI_FILE_SET_ATOMICITY
MPI_FILE_GET_ATOMICITY
----------
Added the following sentences to the introduction of Filetype Constructors:
Note that these datatype constructors create defined datatypes,
not intrinsic or fundamental datatypes. In other words,
datatypes decoded using \func{MPI\_GET\_TYPE\_ENVELOPE} (see
section \ref{subsec:ei-dataaccess}), will not yield ``combiners''
in this section.
----------
Removed MPI_TYPE_DARRAY_2D routine.
----------
Added the following text regarding use of a buffer after a nonblocking
operation is initiated, but before it is completed (see Data Access
section/Synchronism subsection):
Once a nonblocking data access operation is initiated,
accessing the local buffer of the operation, or using it as the
source or target of other communications, before the operation
completes is erroneous.
Note that the subcommittee decided to make the semantics identical
to those of one-sided at the October meeting. However, one-sided
semantics would have only yielded:
...with one exception: the buffer of a nonblocking write
can be used as the source for multiple outstanding writes.
As the ability to perform mulitple nonblocking writes from a single
buffer seems dubious, the semantics have been left equivalent to point
to point communication.
----------
Alphabetized and cleaned up the "Reserved File Hints" section.
----------
Status return values are defined (see WRITE_EXPLICIT, READ_EXPLICIT,
IWRITE_EXPLICIT, and IREAD_EXPLICIT). Fields other than count
and error are undefined.
----------
Added MPI_ERR_QUOTA.
----------
Datatypes must be committed before being used as etypes and filetypes.
----------
Moved filetype constructor examples to Examples section.
----------