Hi Max:
You say that that the function keeps "allocating memory in the pml free list."  
How do you know that is happening? 
Do you know which free list it is happening on?  There are something like 8 
free lists associated with the pml ob1 so it would be interesting to know which 
one you observe is growing.

Rolf 

>-----Original Message-----
>From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Max Staufer
>Sent: Wednesday, September 11, 2013 10:23 AM
>To: de...@open-mpi.org
>Subject: [OMPI devel] Nearly unlimited growth of pml free list
>
>Hi All,
>
>     as I already asked in the users list, I was told thats not the right 
> place to ask,
>I came across a "missbehaviour" of openmpi version 1.4.5 and 1.6.5 alike.
>
>the mca_pml_ob1_send function keeps allocating memory in the pml free list.
>It does that indefinitly. In my case the list grew to about 100Gb.
>
>I can controll the maximum using the pml_ob1_free_list_max parameter, but
>then the application just stops working when this number of entries in the list
>is reached.
>
>The interesting part is that the growth only happens in a single place in the
>code, which is RECURSIVE SUBROUTINE.
>
>And the called function is an MPI_ALLREDUCE(... MPI_SUM)
>
>Apparently its not easy to create a test program that shows the same
>behaviour, just recursion is not enought.
>
>Is there a mca parameter that allows to limit the total list size without 
>making
>the app. stop ?
>
>or is there a way to enforce the lock on the free list entries ?
>
>Thanks for all the help
>
>Max
>_______________________________________________
>devel mailing list
>de...@open-mpi.org
>http://www.open-mpi.org/mailman/listinfo.cgi/devel
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may 
contain
confidential information.  Any unauthorized review, use, disclosure or 
distribution
is prohibited.  If you are not the intended recipient, please contact the 
sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------

Reply via email to