Moving to devel; this question seems worthwhile to push out to the
general development community.
I've been coming across an increasing number of customers and other
random OMPI users who use system(). So if there's zero impact on
performance and it doesn't make the code [more] incredibly
On the other hand, since the MPI standard explicitly says you're not
allowed to call fork() or system() during the MPI application and
sense the network should really cope with this in some way, if it
further complicates the code *at all*, I'm strongly against it.
Especially since it won't
Jeff Squyres wrote:
Moving to devel; this question seems worthwhile to push out to the
general development community.
I've been coming across an increasing number of customers and other
random OMPI users who use system(). So if there's zero impact on
performance and it doesn't make the co
Brian Barrett wrote:
On the other hand, since the MPI standard explicitly says you're not
allowed to call fork() or system() during the MPI application and
Does it ? The MPI spec says that you should not access buffers that have
been committed to MPI (pending asynchronous send or recv buffe
The fork() problem is due to memory registration aggravated by
registration cache. Memory registration in itself is a hack from
the OS
point of view, and you already know a lot about the various problems
related to registration cache.
So Gleb is indicating that this is a problem in the pipeli
gshipman wrote:
The fork() problem is due to memory registration aggravated by
registration cache. Memory registration in itself is a hack from
the OS
point of view, and you already know a lot about the various problems
related to registration cache.
So Gleb is indicating that this is a probl
