Depending on the setup, threads often get allocated a thread local
stack with size equal to the stacksize rlimit. Two threads maybe?
David
Terry Dontje wrote:
A couple things to note. First Sun MPI 8.2.1 is effectively OMPI
1.3.4. I also reproduced the below issue using a C code so I think
A couple things to note. First Sun MPI 8.2.1 is effectively OMPI
1.3.4. I also reproduced the below issue using a C code so I think this
is a general issue with OMPI and not Fortran based.
I did a pmap of a process and there were two anon spaces equal to the
stack space set by ulimit.
In
Hi all,
I'm trying to interleave computation with communication. As a result, I have
resorted to using MPI with POSIX threads. Primarily, I am trying to
communicate a partial vector v3 while computing an inner product v1*v2 (mod
q). To give you an idea of the platform and the libraries:
1. Intel
People can correct me if I am wrong, but are you NOT suppose to run
applications directly and only suppose to submit them using the batch process
"qsub" to prevent all this overuse of resources?
> Date: Thu, 19 Nov 2009 19:21:46 +0100
> From: kapi...@rz.rwth-aachen.de
> To:
Hi volks,
we see an exeedingly *virtual* memory consumtion through MPI processes
if "ulimit -s" (stack size)in profile configuration was setted higher.
Furthermore we believe, every mpi process started, wastes about the
double size of `ulimit -s` value which will be set in a fresh console
