Re: [OMPI users] Determining what parameters a scheduler passes to OpenMPI

Sorry about the comment re cpus-per-proc - confused this momentarily with another user also using Torque. I confirmed that this works fine with 1.6.5, and would guess you are hitting some bug in 1.6.0. Can you update? On Jun 6, 2014, at 12:20 PM, Ralph Castain wrote: > You

Re: [OMPI users] Bind multiple cores to rank - OpenMPI 1.8.1

It's a good idea to provide the default setting for the modifier pe. Okay, I can take a look to review but a bit busy now, so please give me a few days. Regards, Tetsuya > Okay, I revised the command line option to be a little more user-friendly. You can now specify the equivalent of the old

Re: [OMPI users] Bind multiple cores to rank - OpenMPI 1.8.1

I'm having no luck poking at this segfault issue. For some strange reason, we seem to think there are coprocessors on those remote nodes - e.g., a Phi card. Yet your lstopo output doesn't seem to show it. Out of curiosity, can you try running this with "-mca plm rsh"? This will substitute the

Re: [OMPI users] Bind multiple cores to rank - OpenMPI 1.8.1

Okay, I revised the command line option to be a little more user-friendly. You can now specify the equivalent of the old --cpus-per-proc as just "--map-by :pe=N", leaving the mapping policy set as the default. We will default to NUMA so the cpus will all be in the same NUMA region, if possible,

Re: [hwloc-users] divide by zero error?

I added --disable-cpuid, will be in hwloc v1.10. Brice Le 06/05/2014 00:44, Friedley, Andrew a écrit : > Actually, is there any way to make HWLOC_COMPONENTS=-x86 the default or > otherwise disable or compile without the x86 backend, so that I get that > behavior by default? > > Thanks, > >