Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Issues on install 1.3.1
From: Gus Correa (gus_at_[hidden])
Date: 2009-04-02 14:45:38

Hi Francesco, list

I was thinking of compatibility (and consistency)
rather than of performance.
I don't know about Debian, but on CentOS 5.2 x86_64
the 64-bit libnuma library lives at /usr/lib64,
and the 32-bit version on /usr/lib.

If you are trying to build 64-bit OpenMPI libraries with libnuma
support, it sounds to me that the natural path to choose is /usr/lib64.

Sorry, I don't have an answer about performance.
You may need to ask somebody else or google around
about the relative performance of 32-bit vs. 64-bit mode.

Gus Correa
Gustavo Correa
Lamont-Doherty Earth Observatory - Columbia University
Palisades, NY, 10964-8000 - USA

Francesco Pietra wrote:
> Gustavo:
> Does this imply that a compilation with "--with-libnuma=/usr/lib64"
> may afford better performance?
> Am asking that because in the meantime I have taken previous
> compilation of openmpi-1.2.6 and use it (one disk of raid1 died and I
> changed both with larger ones). If better performance I can try to
> replace openmpi with the latest version and libnuma pointing to 64.
> thanks
> francesco
> On Thu, Apr 2, 2009 at 6:10 PM, Gus Correa <gus_at_[hidden]> wrote:
>> Hi Francesco, list
>> Francesco:
>> Besides the typo that Jeff found on your
>> CXX definition, I would guess you want
>> --with-libnuma=/usr/lib64
>> (since your machine is amd64,
>> and you are using the 64-bit Intel compilers: cce, fce).
>> That is instead of --with-libnuma=/usr/lib (32-bit).
>> The /usr/lib64 path also works for other extra libraries
>> (e.g. Torque, Infiniband) on Linux x86_64.
>> This is what I used on our AMD x86_64 with CentOS 5.2, and it works.
>> My two cents,
>> Gus Correa
>> ---------------------------------------------------------------------
>> Gustavo Correa
>> Lamont-Doherty Earth Observatory - Columbia University
>> Palisades, NY, 10964-8000 - USA
>> ---------------------------------------------------------------------
>> Jeff Squyres wrote:
>>> On Apr 2, 2009, at 7:21 AM, Francesco Pietra wrote:
>>>> Hi:
>>>> With debian linux amd64 lenny I tried to install openmpi-1.3.1 instead
>>>> of using the executables openmpi-1.2.6 of previous disks. I configured
>>>> as for 1.2.6 (wrong ?)
>>>> CC=/opt/intel/cce/10.1.015/bin/icc CXX=opt/intel/cce/10.1.015/bin/icpc
>>> Don't you need a / in the beginning of the CXX definition?
>>>> F77=/opt/intel/fce/10.1.015/bin/ifort
>>>> FC=/opt/intel/fce/10.1.015/bin/ifort --with-libnuma=/usr/lib
>>>> getting:
>>>> checking whether using GNU C++ compiler .. yes
>>>> dependency style icpc ... gcc3
>>>> checking how to run C++ preprocessor ... /lib/cpp
>>>> checking for compiler vendor ... intel
>>>> cheching if C++ compiler works .. NO
>>>> it is not clear to me to which compiler NO refers: gcc or intel? I
>>> I would assume the C++ compiler is icpc since it's in your (abbreviated)
>>> output shown above.
>>>> would also appreciate very much a direction how to chech gcc and intel
>>>> C++ independently.
>>> I'm not sure what you're asking here..? Open MPI's configure has 2
>>> independent sections checking characteristics of the C and C++ compilers.
>> _______________________________________________
>> users mailing list
>> users_at_[hidden]
> _______________________________________________
> users mailing list
> users_at_[hidden]