On Jan 9, 2009, at 12:39 AM, William Hachfeld wrote:
Can any of the OpenMPI developers speculate as to possible
mechanisms by which the ptrace() attachment , signal handler, or
timer registration and corresponding signal delivery could cause
large amounts of time to be spent within the "pro
There might be one reason to slowdown the application quite a bit. If
the fact that you're using timer interact with the libevent (the
library we're using to internally manage any kind of events), then we
might end-up in the situation where we call the poll for every
iteration in the event
I'm trying to understand how much shared memory is allocated when
maffinity is on.
The sm BTL sets up a file that is mmapped into each local process's
address space so that the processes on a node can communicate via shared
memory.
Actually, when maffinity indicates that there are multiple "
I don't see much harm in including this as long as rpath builds are
still the default. If there's a non-default option to disable rpath
builds, that would be fine with me.
Does this patch disable rpath by default, or do you have to explicitly
use the --disable-rpath flag to configure?
O
I will see what I can do. BTW, what kind of integration are you looking
for? Do you just want the changeset to be logged in the Trac bug via a
hook that looks at the comment for the appropriate bug number? Or
something different?
Paul Franz
Jeff Squyres wrote:
Greetings Paul. Since I was the
