Hello List,
Dirk Eddelbuettel wrote:
On 3 April 2009 at 06:35, Jerome BENOIT wrote:
| It appeared that the file /etc/openmpi/openmpi-mca-params.conf on node green
was the only one
| into the cluster to contain the line
|
| btl_tcp_port_min_v4 = 49152
Great -- so can we now put your claims of
Hello List !
George Bosilca wrote:
The range of ports for the OOB TCP has been removed by commit r20390.
Apparently it was replaced by the static port functionality. Only the
TCP BTL use the range mechanism.
if applicable, what is the parameter name for the this static port ?
Thanks in adv
As far as I understand,
apt-get install libnuma1 libnuma-dbg libnuma-dev
installs libnuma libraries 64 bit in /usr/lib there also two symlinks
/usr/lib32 and /usr/lib64 but there is no trace of the libnuma
libraries there.
That the computational codes I use run twice as fast at 64 bit than 32 bi
Sorry for such pedestrian misprint.
Corrected, the configure ended with error:
"Expected file /usr/lib/include/numa.h"
In debian amd64 lenny it has a different location:
"/usr/include/numa.h"
Can the configure script be modified safely to account for the
different location?
thanks
francesco
On Apr 3, 2009, at 3:36 AM, Jerome BENOIT wrote:
> This seems to be a local admin issue as such a line is unlikely to
have been
> added by either the Debian Open MPI or slurm packages.
This is clearly an admin issue: maintaining a cluster of clones is
quite a challenge :-)
It certain
What George is saying is that OMPI has two different systems that use
sockets: the BTL (MPI communications) and the OOB (OMPI's internal
management communications).
We've been talking about the TCP BTL parameters over the rest of this
thread.
For the TCP OOB, it looks like the parameter n
> Hello,
>
> I am trying to compile OpenMPI on a Red Hat Enterprise Linux 5 platform with
> the Sun Studio 12 compiler suite. (I currently have the Red Hat-bundled
> OpenMPI w/GNU compilers running).
>
> I have already encountered and addressed the problem of the C++ compiler not
> working in
Thanks for the reply !
I asked because
ompi_info --param all all | grep static
gave nothing.
This feature is certainly for the coming version.
Jeff Squyres wrote:
What George is saying is that OMPI has two different systems that use
sockets: the BTL (MPI communications) and the OOB (OMPI's
Hi -
Unfortunately, as the bug at Sun's web site points out, their compiler is
borked. There's not a lot we can do about that fact, without causing a
whole host of other problems.
If you aren't using C++, I'd recommend compiling Open MPI with GCC and
then reseting the wrapper compilers to i
Gahh -- you're right. I accidentally checked our development trunk,
not the released v1.3 series... Sorry for the confusion.
George, too, was referring to something that happened on our
development trunk, not the v1.3 series.
On Apr 3, 2009, at 10:16 AM, Jerome BENOIT wrote:
Thanks for
Which version of the Sun Studio compilers are you using also which
version of OMPI are you trying to build. I am successful with building
OMPI with the Sun Studio Express release 200811 on Linux systems if I
don't use the C++ compiler. Prior releases we did suffer from some
issues. A "cc -V"
I am posting again more specifically because it may have been buried
in a more generic thread.
With debian linux amd64 lenny and openmpi-1.3.1
./configure cc=/opt/intel/cce/10.1.015/bin/icc
cxx=/opt/intel/cce/10.1.015/bin/icpc
F77=/opt/intel/fce/10.1.015/bin/ifort
FC=/opt/intel/fce/10.1.015/bin/i
2009/4/3 Francesco Pietra :
> > "expected file /usr/lib/include/numa.h was not found"
>
> In debian amd64 lenny numa.h has a different location
> "/usr/include/numa.h". Attached is the config.log.
>
> I would appreciate help in circumventing the problem.
It is /usr/include/numa.h on SuSE also (SLE
I was not sure whether that is a technically correct procedure. It works. Thanks
francesco
On Fri, Apr 3, 2009 at 6:05 PM, John Hearns wrote:
> 2009/4/3 Francesco Pietra :
>> > "expected file /usr/lib/include/numa.h was not found"
>>
>> In debian amd64 lenny numa.h has a different location
>> "/u
2009/4/3 Francesco Pietra :
> I was not sure whether that is a technically correct procedure. It works.
> Thanks
>
It most certainly is not. But I have been a Unix system admin for many
years. I have done things which I am
not proud of
If I ever offer to let you use my keyboard, wash your
"I was not sure" before your mail. I was sure after that.
I'm a chemist with little knowledge of systems. I used in the past to
make symlinks to outdated or upgraded libraries. It worked, but I was
aware of the risk. This case has no risk. I was in a mess, now partly
out. The code I'm interested i
16 matches
Mail list logo
