Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DART locality interface requires mpirun mapping option for OpenMPI #230

Open
rkowalewski opened this issue Jan 4, 2017 · 0 comments
Open

Comments

@rkowalewski
Copy link

rkowalewski commented Jan 4, 2017

The DART Locality interface does not work if OpenMPI is started with the mpirun default setting. This manifests in an erroneous locality hierarchy information, e.g. an invalid number of NUMA domains. On a local development system (projekt03) I can see 4 NUMA domains while there actually exist only 2. For whatever reason this depends on the process mapping. The issue currently causes strange behavior in DART.

In order to fix that we have to start with mpirun --map-by core -n [NPROCS] ./app. This yields a correct locality information in DART. Maybe other options work as well, however, not with the default which is socket.

I have checked this with OpenMPI versions 1.10.x and 2.0.x. Intel MPI, MVAPICH and MPICH work fine.

@rkowalewski rkowalewski self-assigned this Jan 4, 2017
@rkowalewski rkowalewski changed the title Dart Locality Interface Dart Locality Interface does not work with OpenMPI Jan 4, 2017
@fuchsto fuchsto changed the title Dart Locality Interface does not work with OpenMPI DART locality interface requires mpirun mapping option for OpenMPI Jan 6, 2017
@fuchsto fuchsto added this to the dash-0.4.0 milestone Feb 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants