Hi,
I think this is the fix for broken trunk
submitted in r20439.
Index: orte/tools/orte-bootproxy/Makefile.am
===
--- orte/tools/orte-bootproxy/Makefile.am (revision 20438)
+++ orte/tools/orte-bootproxy/Makefile.am (wor
On Feb 4, 2009, at 10:17 AM, Christoph van Wüllen wrote:
I came across OpenMPI because it seems to be the only MPI
implementation
which supports 64-bit integers in FORTRAN, so I had a huge propensity
stepping into this bug.
Since I was the one that championed the whole "what if fortran
IN
In btl_sm_component.c, mca_btl_sm_component_progress() polls on FIFOs.
If it gets something, it has a "switch" statement with cases for send
fragments, returned fragments (ACKs) to be returned to the freelist, and
default/unknown. What's that default/unknown case about? What behavior
should
I've started a wiki page to keep track of the agenda for the OMPI
Developer meeting that will occur after the MPI Forum meeting. The page
is at:
https://svn.open-mpi.org/trac/ompi/wiki/Feb09Meetingsjc
Feel free to add other topics.
--td
In the pt-2-pt code, the default case should never be hit - it would be a
bug in the code. Don't know about other uses of the sm btl.
Rich
On 2/5/09 12:30 PM, "Eugene Loh" wrote:
> In btl_sm_component.c, mca_btl_sm_component_progress() polls on FIFOs.
> If it gets something, it has a "switch"
BTLs have "add_procs" functions. E.g., my own parochial interests are
with the sm BTL and there is a mca_btl_sm_add_procs() function. I'm
trying to get a feel for how likely it is that this function would be
called more than once. There is code in there to support the case where
it's called
I would leave the code alone. The intent was for (A), but it is not used
for that. It is not in the performance critical region, works correctly as
we use it today, and putting it back later on would be a hassle not needed.
Rich
On 2/5/09 2:41 PM, "Eugene Loh" wrote:
> BTLs have "add_procs"
I would only add that we should be certain that the code is -not-
called more than once as this could cause problems. We don't currently
have a way for dynamically spawned procs to share memory with their
parents - if that code does get called, I would worry that it hadn't
been tested and c
This functionality has as many chances to be called as any MPI 2
dynamics MPI functions. Every time the MPI universe is expanded, once
the modex of the new processes is known, add procs is called in order
to allow the PML and BTL to update their local view of the MPI universe.
The code is r
