+1!
george.
On Nov 5, 2012, at 18:59 , Jeff Squyres wrote:
> +1 on the ompi/mca/btl/openib/btl_openib_mca.c and
> opal/mca/base/mca_base_param.c.
>
> I didn't check the others.
>
>
> On Nov 5, 2012, at 6:31 PM, Nathan Hjelm wrote:
>
>> What: I used valgrind on ompi_info and found several
+1 on the ompi/mca/btl/openib/btl_openib_mca.c and
opal/mca/base/mca_base_param.c.
I didn't check the others.
On Nov 5, 2012, at 6:31 PM, Nathan Hjelm wrote:
> What: I used valgrind on ompi_info and found several leaks in the trunk. This
> patch fixes some of the leaks.
>
> pml/v:
> - If vp
What: I used valgrind on ompi_info and found several leaks in the trunk. This
patch fixes some of the leaks.
pml/v:
- If vprotocol is not being used vprotocol_include_list is leaked. Assume
vprotocol never takes ownership (see below) and always free the string.
coll/ml:
- (patch verified) c
On Thu, Nov 01, 2012 at 07:22:42PM -0400, George Bosilca wrote:
>
> On Nov 1, 2012, at 19:07 , Nathan Hjelm wrote:
>
> > I was going to address this second inconsistency with another patch but now
> > seems like a good time to get a see if anyone has an opinion about how this
> > should be fix
FYI -- George and I updated the wiki this morning:
https://svn.open-mpi.org/trac/ompi/wiki/MPIConformance
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
I just want to publicly thank Josh and DongInn (Indiana U. Sys Admin -- the guy
who handles all of Open MPI's hosting needs) for all the work that was required
to do this move.
None of you saw all the behind-the-scenes work to make this changeover, but let
me tell you: it too many hours of Josh
The MTT server migration went well this weekend. I have updated the
Open MPI website to redirect you appropriately to the new MTT
Reporter.
You will need to update your .ini files to submit your tests to the
new server at the address below:
https://mtt.open-mpi.org/submit/
Let me know if you ex
On Nov 5 2012, Ralph Castain wrote:
We adhere to the MPI standard, so we expect the user in such an instance
to define a datatype that reflects the structure they are trying to send.
We will then do the voodoo to correctly send that data in a heterogeneous
environment, and pass the data back
On Nov 5, 2012, at 10:13 AM, Ralph Castain wrote:
> We adhere to the MPI standard, so we expect the user in such an instance to
> define a datatype that reflects the structure they are trying to send. We
> will then do the voodoo to correctly send that data in a heterogeneous
> environment, and
We adhere to the MPI standard, so we expect the user in such an instance to
define a datatype that reflects the structure they are trying to send. We will
then do the voodoo to correctly send that data in a heterogeneous environment,
and pass the data back (in the defined datatype) to the user o
10 matches
Mail list logo
