Changeset 129

Timestamp:

Aug 1, 2005, 6:31:10 PM (19 years ago)

Author:

ole

Message:

More docu

File:

• pypar/README (modified) (2 diffs)

pypar/README

@@ -65 +65 @@
     MPICH and LAM 7.0 on Solaris (Sun Enterprise)
     MPICH on Linux
-    MPICH on Windows (NT/2000).
+    MPICH on Windows (NT/2000)
+    MPICH for Darwin (Mac OS)
+    LAM/MPI with Linux on Opteron 64 bit
    
   
@@ -171 +173 @@
  lamboot -v lamhosts  
 
+
+HOW DOES PYPAR WORK?
+
+Pypar works as follows
+    1  mpirun starts P python processes as specified by mpirun -np P
+    2  each python process imports pypar which in turn imports a shared
+       library (python extension mpiext.so) that has been statically linked 
+       to the C MPI libraries using e.g. mpicc (or cc -lmpi)
+    3  The Python extension proceeds to call MPI_init with any commandline
+       parameters passed in by mpirun (As far as I remember MPICH uses this 
+       to identify rank and size, whereas LAM doesn't)
+    4  The supported MPI calls are made available to Python through the
+       pypar interface
+
+    If  pypar is invoked sequentially it supports a rudimentary interface
+    with e.g. rank() == 0 and size() == 1
+ 
+ 
+ 
 DOCUMENTATION