Re: [OMPI users] OpenMPI binding all tasks to cpu0, leaving cpu1 idle. (2-cpu system)

Hi, Miguel Figueiredo Mascarenhas Sousa Filipe wrote: Hi there, I have a 2-cpu system (linux/x86-64), running openmpi-1.1. I do not specify a hostfile. Lately I'm having performance problems when running my mpi-app this way: mpiexec -n 2 ./mpi-app config.ini Both mpi-app processes are running

Re: [OMPI users] OpenMPI binding all tasks to cpu0, leaving cpu1 idle. (2-cpu system)

-c, -np, --np, -n, --n all do exactly the same thing. Tim Miguel Figueiredo Mascarenhas Sousa Filipe wrote: Hi, On 10/3/07, jody wrote: Hi Miguel I don't know if it's a typo - but actually it should be mpiexec -np 2 ./mpi-app config.ini and not mpiexec -n 2 ./mpi-app config.ini thanks fo

Re: [OMPI users] OpenMPI binding all tasks to cpu0, leaving cpu1 idle. (2-cpu system)

Hi, On 10/3/07, jody wrote: > Hi Miguel > I don't know if it's a typo - but actually it should be > mpiexec -np 2 ./mpi-app config.ini > and not > > mpiexec -n 2 ./mpi-app config.ini thanks for the remark, you're right, but in the man page says -n is a synonym for -np Kind regards, -- Miguel

Re: [OMPI users] OpenMPI binding all tasks to cpu0, leaving cpu1 idle. (2-cpu system)

Hi Miguel I don't know if it's a typo - but actually it should be mpiexec -np 2 ./mpi-app config.ini and not > mpiexec -n 2 ./mpi-app config.ini Jody

[OMPI users] OpenMPI binding all tasks to cpu0, leaving cpu1 idle. (2-cpu system)

Hi there, I have a 2-cpu system (linux/x86-64), running openmpi-1.1. I do not specify a hostfile. Lately I'm having performance problems when running my mpi-app this way: mpiexec -n 2 ./mpi-app config.ini Both mpi-app processes are running on cpu0, leaving cpu1 idle. After reading the mpirun ma