Good Day,
I'm using Open MPI on a diskless cluster (/tmp is part of a 1m ramdisk), and
I found that after upgrading from v1.1.4 to v1.2 that jobs using np > 4 would
fail to start during MPI_Init, due to what appears to be a lack of space in
/tmp. The error output is:
-
[tpb200:32193] *
On Wed, 8 Nov 2006, Larry Stewart wrote:
Miguel Figueiredo Mascarenhas Sousa Filipe wrote:
H
the MPI model assumes you don't have a "shared memory" system..
therefore it is "message passing" oriented, and not designed to
perform optimally on shared memory systems (like SMPs, or numa-CCs).
For
On Fri, 18 Aug 2006, Steven A. DuChene wrote:
I am attempting to build OpenMPI-1.1 on a RHEL4u2 system that has
the standard gfortran install as part of the distro and with a self installed
recent version of g95 from g95.org but when I use the FC flag to
configure to tell it where to find the g95
On Wed, 16 Aug 2006, Allan Menezes wrote:
Hi AnyOne,
I have an 18 node cluster of heterogenous machines. I used fc5 smp
kernel and ocsar 5.0 beta.
I tried the following out on a machine with Open mpi 1.1 and 1.1.1b4
versions. The machine consists of a Dlink 1gigb/s DGE-530T etherent card
2.6
However, when I used openmpi to compile a application program( Molecular
dynamcis code: Amber9), error messages are given:
I think you would be better off using the OpenMPI wrapper compilers rather than
trying to link the mpi libraries by hand. For mo
re information read the FAQ, which contain
FWIW, I know that we saw similar issues with the Intel 8.1 series
(segv's during compilation). Since we are not doing anything illegal in
terms of C++, we already treated this as a compiler bug that we couldn't
really do much about. Plus, we [perhaps incorrectly] assumed that most
sites using th
I am trying to build OpenMPI v1.0.2 (stable) on an Opteron using the v8.1 Intel
EM64T compilers:
Intel(R) C Compiler for Intel(R) EM64T-based applications, Version 8.1 Build
20041123 Package ID: l_cce_pc_8.1.024
Intel(R) Fortran Compiler for Intel(R) EM64T-based applications, Version 8.1
Build
e only BTL component that has async progress support implemented
anyway; sm *may*, but I'd have to go back and check)? Leave MPI threads
enabled (i.e., MPI_THREAD_MULTIPLE) and see if that gets you further.
Hugh Merz wrote:
It's still only lightly tested. I'm surprised that it tota
.
Thanks,
Hugh
Hugh Merz wrote:
Howdy,
I tried installing the release candidate with thread support
enabled ( --enable-mpi-threads and --enable-progress-threads ) using an
old rh7.3 install and a recent fc4 install (Intel compilers). When I try
to run a simple test program, the executab
Howdy,
I tried installing the release candidate with thread support
enabled ( --enable-mpi-threads and --enable-progress-threads ) using an
old rh7.3 install and a recent fc4 install (Intel compilers). When I try
to run a simple test program, the executable, mpirun and orted all sleep
in wh
10 matches
Mail list logo