The keyword here is consolidation. It's not about violating the initial design,
it is more about keeping the design consistent. I think this change is good
from an overall perspective, but now we have two ways to report similar types
of problems. In other words, I don't see how we can fail sendi
If you use any kind of high performance network that require memory
registration for communications, then this high cost for the MPI_Alloc_mem will
be hidden by the communications. However, the MPI_Alloc_mem function seems
horribly complicated to me, as we do the whole "find-the-right-allocator"
Thanks, I will apply the patch to all branches later today. Thanks for your
help!
George
"All the books in the world contain no more information than is broadcast as
video in a single large American city in a single year. Not all bits have equal
value.". -- Carl Sagan
On Apr 23, 2010, at 3
其他的都没变，主要是添加了一下使用说明。
ht模块的相关配置说明V3.docx
Description: MS-Word 2007 document
Thank you, George!
I checked out trunk version 1.7a1r23028 and got the same errors as on
1.4.*. Then I applied your patch, fixed one more file
Index: pml_ob1_recvreq.c
===
--- pml_ob1_recvreq.c (revision 23028)
+++ pml_ob1_recvreq.
Timur,
Thanks for the very detailed analysis of the problem. Based on your
observations, I was able to track down the issue pretty quickly. In few words,
the 64 bits machine sent a pointer to the 32 bits one, and expected that it
will get it back untouched. Unfortunately, on the 32 bits machine
Hi folks
Per the last telecon and some email threads, I have updated the errmgr
framework to allow a greater range of response options and remove several
loopback messages. See the commit message for more description of what was done:
https://svn.open-mpi.org/trac/ompi/changeset/23023
Please n
