Does anyone have any opinions on this? If not, I'll go implement
option #1.
Len: can we add this to the agenda for tomorrow? It should take <5
minutes to discuss.
Begin forwarded message:
From: "Open MPI"
Date: July 23, 2007 9:13:47 PM EDT
Cc: b...@osl.iu.edu
Subject: [Open MPI] #1101
Excellent point. Thanks!
I think that this will require a little tomfoolery to fix properly
because we can't simply return NULL (you can't expect to use the
pointer that we return to store anything, but you should be able to
expect to be able to dereference it without seg faulting).
I'll
If I understand correctly the standard,
http://www.mpi-forum.org/docs/mpi-20-html/node54.htm#Node54
MPI_ALLOC_MEM with size=0 is valid ('size' is a nonnegative integer)
Then, using branch v1.2, I've got the following warning at runtime:
malloc debug: Request for 0 bytes (base/mpool_base_alloc.c
Using a fresh (2 hours agoo) update of SVN branch v1.2, I've found
that attribute MPI_APPNUM returns -1 (minus one) when an 'sequential'
application is not launched through mpiexec.
Reading the MPI standard, I understand it should return a non-negative
integer if defined, or it should not be defi
Matt,
Sorry for the delay in replying.
>first of all, thanks for the info bill! i think i'm really starting to
piece things together now. you are right in
>that i'm working with a 6.x (6.2 with 6.1 devel libs ;) install here at
cadence, without the HPC extensions AFAIK.
>also, i think that are c
Just committed r15557 that adds finalize
flow to mpool. So now openib should be able to release
all resources in normal way.
Pasha
Pavel Shamis (Pasha) wrote:
Jeff Squyres wrote:
Background: Pasha added a call in the openib BTL finalize function
that will only succeed if all registered m
