I can build OpenMPI with FT on my system if I'm using 1.4 source, but
if I use any of the 1.5 series, I get hung in a strange "no" loop at the
beginning of the compile (see below):
+ ./configure --build=x86_64-unknown-linux-gnu
--host=x86_64-unknown-linux-gnu --target=x86_64-redhat-linux-gnu
--pr
Solved: The process to core locking was due to affinity being set at
the PSM layer. So I added -x IPATH_NO_CPUAFFINITY=1 to the mpirun
command.
Dave
On Wed, Aug 4, 2010 at 12:13 PM, Eugene Loh wrote:
>
> David Akin wrote:
>
>> All,
>> I'm trying to get the OpenMP po
e bound. It appears
> that MPI_Get_processor_name is simply returning the name of the node as
> opposed to the name/id of any specific core. How do you know what core the
> thread is actually executing on?
>
>
>
> This would tell you if your code was bouncing between cores.
>
> On J
ph, as to why no options is
> causing your code bind. Maybe add a --report-bindings to your mpirun line
> to see what OMPI thinks it is doing in this regard?
>
>
> This is a good suggestion - I'm beginning to believe that the binding is
> happening in the user's app a
estion - I'm beginning to believe that the binding is
> happening in the user's app and not OMPI.
>
>
> --td
>
> --td
>
> On Jul 28, 2010, at 5:47 PM, David Akin wrote:
>
>
>
> All,
> I'm trying to get the OpenMP portion of the code below to run
-not- bind. Check your
> default mca param file and your environment. Do you have any mca params set
> in them?
>
>
> On Jul 28, 2010, at 9:40 PM, David Akin wrote:
>
>> Here's the exact command I'm running when all threads *are* pinned to
>>
ed threads.
>
>
> On Jul 28, 2010, at 5:47 PM, David Akin wrote:
>
>> All,
>> I'm trying to get the OpenMP portion of the code below to run
>> multicore on a couple of 8 core nodes.
>>
>> Good news: multiple threads are being spawned on each node
All,
I'm trying to get the OpenMP portion of the code below to run
multicore on a couple of 8 core nodes.
Good news: multiple threads are being spawned on each node in the run.
Bad news: each of the threads only runs on a single core, leaving 7
cores basically idle.
Sorta good news: if I provide a
All,
I'm trying to get the OpenMP portion of the code below to run
multicore on a couple of 8 core nodes.
Good news: Multiple threads are being spawned on each node in the run.
Bad news: Each of the threads only runs on a single core, leaving 7
cores basically idle.
Sorta good news: If I provide a
