summaryrefslogtreecommitdiffstats
path: root/release_docs/INSTALL_parallel
diff options
context:
space:
mode:
authorAlbert Cheng <acheng@hdfgroup.org>2013-03-05 22:35:23 (GMT)
committerAlbert Cheng <acheng@hdfgroup.org>2013-03-05 22:35:23 (GMT)
commit5b959f0bf95b0a50933e57cee0c1e86a318f6d39 (patch)
treec2097d002591b184bf83b2159bf906865344b2b0 /release_docs/INSTALL_parallel
parent2195fe47db5cd5f8e298ec455c4e34cfdd301b9b (diff)
downloadhdf5-5b959f0bf95b0a50933e57cee0c1e86a318f6d39.zip
hdf5-5b959f0bf95b0a50933e57cee0c1e86a318f6d39.tar.gz
hdf5-5b959f0bf95b0a50933e57cee0c1e86a318f6d39.tar.bz2
[svn-r23327] Added the reference of the requirement of POSIX Compliance.
Diffstat (limited to 'release_docs/INSTALL_parallel')
-rw-r--r--release_docs/INSTALL_parallel28
1 files changed, 22 insertions, 6 deletions
diff --git a/release_docs/INSTALL_parallel b/release_docs/INSTALL_parallel
index b2e1eec..eacaf68 100644
--- a/release_docs/INSTALL_parallel
+++ b/release_docs/INSTALL_parallel
@@ -17,12 +17,14 @@ of running the parallel test suites.
1.1. Requirements
-----------------
-PHDF5 requires an MPI compiler with MPI-IO support and a parallel file system.
-If you don't know yet, you should first consult with your system support staff
-of information how to compile an MPI program, how to run an MPI application,
-and how to access the parallel file system. There are sample MPI-IO C and
-Fortran programs in the appendix section of "Sample programs". You can use
-them to run simple tests of your MPI compilers and the parallel file system.
+PHDF5 requires an MPI compiler with MPI-IO support and a POSIX compliant
+(Ref. 1) parallel file system. If you don't know yet, you should first consult
+with your system support staff of information how to compile an MPI program,
+how to run an MPI application, and how to access the parallel file system.
+There are sample MPI-IO C and Fortran programs in the appendix section of
+"Sample programs". You can use them to run simple tests of your MPI compilers
+and the parallel file system. Also, the t_posix_compliant test in testpar
+verifies if the file system is POSIX compliant.
1.2. Further Help
@@ -274,6 +276,20 @@ if the tests should use directory /PFS/user/me, do
shell initial files like .profile, .cshrc, etc.)
+Reference
+---------
+1. POSIX Compliant. A good explanation is by Donald Lewin,
+ After a write() to a regular file has successfully returned, any
+ successful read() from each byte position on the file that was modified
+ by that write() will return the date that was written by the write(). A
+ subsequent write() to the same byte will overwrite the file data. If a
+ read() of a file data can be proven by any means [e.g., MPI_Barrier()]
+ to occur after a write() of that data, it must reflect that write(),
+ even if the calls are made by a different process.
+ Lewin, D. (1994). "POSIX Programmer's Guide (pg. 513-4)". O'Reilly
+ & Associates.
+
+
Appendix A. Sample programs
---------------------------
Here are sample MPI-IO C and Fortran programs. You may use them to run simple