FYI: discussions of Open MPI internals should be on the de...@open-mpi.org
list, not the us...@open-mpi.org list. I mention this because not all OMPI
developers are on the users list.
On Sep 9, 2013, at 3:59 AM, Max Staufer wrote:
> I am still working on a small example that shows the proble
I am still working on a small example that shows the problem,
our problematic call is part of a fairly extensive framework so its not
easy to post that part, but see below.
As you can see the subroutine is recursive and will be calling itself
again depending on the outcome posted here.
The MPI
Yes, the number of elements each freelist accepts to allocate can be bounded.
However, we need to know which freelist we should act upon.
What exactly you means by "MPI_ALLREDUCE is called in a recursive way"? You
mean inside a loop right?
George.
On Sep 8, 2013, at 21:36 , Max Staufer wro
I will post a small example for testing.
It is interesting to note though that this happens only
when MPI_ALLREDUCE is called in a recursive kind of way.
Is there a possibility to limit the OMPI_free_list groth, via an --mca
parameter ?
List-Post: users@lists.open-mpi.org
Date: Sun, 08
This is not supposed to happen. Can you please post an example highlighting
this behavior?
George.
On Sep 8, 2013, at 14:51 , Max Staufer wrote:
> Hi All,
>
> using ompi 1.4.5 or 1.6.5 for that matter, I came across an
> interesting thing
>
> when an MPI function is called from in a recus
