On Sep 1, 2012, at 7:33 AM, Zbigniew Koza wrote: > the new syntax works well (I used "man mpirun", which displayed the old > syntax). > Also, the report displayed by --report-binding is far more human-readable > than in previous versions of OpenMPI > > Out of curiosity, and also to supress the warning, I installed the > libnuma-dev package with libnuma.so and libnuma.a libraries, but the warning > remains. > Does it mean I should recompile OpenMPI to get rid of this warning?
I'm a little confused by your mails and questions. Your first mail indicated that you were running OMPI v1.4.3. Did you upgrade to another version (e.g., 1.7.x or 1.9.x)? I ask because you said the new syntax worked, but it shouldn't have back in the 1.4.x series. It doesn't in the 1.6.x series, either. Just to clarify, we do development of Open MPI in pairs of series: - 1.3.x: ancient "feature" OMPI series, evolved into 1.4.x - 1.4.x: previous stable OMPI series, evolved from 1.3.x - 1.5.x: previous "feature" OMPI series, evolved into 1.6.x - 1.6.x: current stable OMPI series, evolved from 1.5.x - 1.7.x: upcoming "feature" OMPI series (not yet released) - 1.8.x: does not yet exist, but will someday be the evolution of 1.7.x - 1.9.x: Open MPI development HEAD Is there any possibility that you're mixing and matching OMPI versions here? E.g., did you see the OMPI v1.4 mpirun(1) man page? Also, yes, if you installed libnuma after installing Open MPI, then you'll need to re-build Open MPI. That being said, Open MPI 1.6 and beyond does not require libnuma for process binding. It does need libnuma for memory binding, though (hwloc uses libnuma behind the scenes for memory binding; libnuma is currently the only public API for memory binding in Linux). -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
