Changes between Version 46 and Version 47 of MpiKernels

Timestamp:

02/29/12 10:33:14 (13 years ago)

Author:

mmamonski

Comment:

--

MpiKernels

@@ -147 +147 @@
 }}}
 * A separate Java Virtual Machine is started for every MPI process what increases significantly the memory footprint of the whole application.
-* MPI kernel must be the sole kernel of the particular MUSCLE instance (for this reason, in our example we had to start `plumber` kernel in separate MUSCLE instance).
-* Many MPI implementations exploits low level optimization techniques (like Direct Memory Access) that may cause crash of Java Virtual Machine.
-* Using MPI to start many  Java Virtual Machines, which loads some native dynamic-link library that later calls MPI routines is something that most people rarely do. In case of problems you might not found any help (you have been warned! ;-).
+* MPI kernel must be the sole kernel of the particular MUSCLE instance (for this reason, in our example we had to start the `plumber` kernel in a separate MUSCLE instance).
+* Many MPI implementations exploit low level optimization techniques (like Direct Memory Access) that may cause a crash of Java Virtual Machine.
+* Using MPI to start many  Java Virtual Machines, which loads native dynamic-link library that later calls MPI routines is something that most people rarely do. In case of problems you might not found any help (you have been warned! ;-).
 
 == MPI Kernels as standalone executables ==