Hi,
thank you very much for your help. Now the command with "-npersocket"
works. Unfortunately it is not a solution for the other problem, which
I reported a few minutes ago.
tyr fd1026 191 cat host_sunpc0_1
sunpc0 sockets=2 slots=4
sunpc1 sockets=2 slots=4
tyr fd1026 192 mpiexec -report-bindin
Okay, I looked at this and the problem isn't in the code. The problem is that
the 1.6 series doesn't have the more sophisticated discovery and mapping
algorithms of the 1.7 series. In this case, the specific problem is that the
1.6 series doesn't automatically detect the number of sockets on a n
On Oct 2, 2012, at 2:44 AM, Siegmar Gross
wrote:
> Hi,
>
> I tried to reproduce the bindings from the following blog
> http://blogs.cisco.com/performance/open-mpi-v1-5-processor-affinity-options
> on a machine with two dual-core processors and openmpi-1.6.2. I have
> ordered the lines and remo
Hi,
I tried to reproduce the bindings from the following blog
http://blogs.cisco.com/performance/open-mpi-v1-5-processor-affinity-options
on a machine with two dual-core processors and openmpi-1.6.2. I have
ordered the lines and removed the output from "hostname" so that it
is easier to see the bi
