Isn't it up to the OS scheduler what gets run where?
> We have an 8-way, 32-core AMD processor machine (single system image)
> and are at present running OpenMPI 1.2.8 . Jobs are launched locally on
> the machine itself. As far as I can see, there doesn't seem to be any
> way to tell OpenMPI
Hi
I am trying to use the PMPI interface with OPENMPI to profile a fortran
program.
I have tried with 1.28 and 1.3rc1 with --enable-mpi-profile switched on.
The problem seems to be that if one eg. intercepts to call to
mpi_comm_rank_ (the fortran hook) then calls pmpi_comm_rank_ this then
In general, Open MPI just uses whatever name mangling scheme the
compiler uses. Hence, if you compile your app and Open MPI with the
same compiler, it should just work. That being said, if your CLM app
is supplying its own name mangling scheme flags to the PGI compiler
(i.e., shifting it
Ralph H. Castain wrote:
> I confess to confusion. OpenMPI will by default map your processes in
> a round-robin fashion based on process slot. If you are in a resource
> managed environment (e.g., TM or SLURM), then the slots correspond to
> cores. If you are in an unmanaged environment, then
We have an 8-way, 32-core AMD processor machine (single system image)
and are at present running OpenMPI 1.2.8 . Jobs are launched locally on
the machine itself. As far as I can see, there doesn't seem to be any
way to tell OpenMPI to launch the MPI processes on adjacent cores.
Presumably such
I'm using OpenMPI 1.2.5 and PGI 7.1.5 compiler suite to get CLM 3.5
working correctly. When compiling for OpenMPI, I encounter the following
snippet of errors -
areaMod.o(.text+0x98a0): In function `areamod_map_checkmap_':
: undefined reference to `mpi_reduce_'
areaMod.o(.text+0x9b6c): In
Matthias,
Thank you for the heads up. I'll work on a fix that uses the
cr_request_checkpoint() interface instead of cr_request_file() when
appropriate.
I filed a ticket about it if you are interested in tracking the
progress on this bug:
https://svn.open-mpi.org/trac/ompi/ticket/1691
Hi!
Berkely recently released a new version of their BLCR. They already
marked the function cr_request_file as deprecated in BLCR 0.7.3. Now
they removed deprecated functions from libcr API.
Since checkpointing support of OMPI is using cr_request_file, all
checkpointing operations fail with
Good morning,
after installing pwscf and running an example, I got a warning message
related to the MCA parameter. To fix it I have tried all the steps indicated in
the FAQ link but it doesn't work. please which command I have to use and from
which directory can use it. perhaps I didn't
