Thanks, Ralph. We'll have a look. Admittedly, we've done little testing with
the tcp BTL - I was under the impression that the yoda interface was capable of
working with all BTLs, seems we need more testing. For sure it works with SM
and OpenIB BTLs.
Josh
-Original Message-
From: dev
Here's the backtrace:
(gdb) where
#0 0x in ?? ()
#1 0x7fac6b8d8921 in mca_bml_base_get (bml_btl=0x239a130, des=0x220e880)
at ../../../../ompi/mca/bml/bml.h:326
#2 0x7fac6b8db767 in mca_spml_yoda_get (src_addr=0x601500, size=4,
dst_addr=0x7fff3b00b370, src=1) at spml_yo
Hmmm...well, it works fine as long as the procs are on the same node. However,
if they are on different nodes, it segfaults:
[rhc@bend002 shmem]$ shmemrun -npernode 1 ./test_shmem
running on bend001
running on bend002
[bend001:06590] *** Process received signal ***
[bend001:06590] Signal: Segment
Ralph,
There is OpenSHMEM test suite
http://bongo.cs.uh.edu/site/sites/default/site_files/openshmem-test-suite-release-1.0d.tar.bz2
The test-suite exercises most of the API.
Best,
Pavel (Pasha) Shamis
---
Computer Science Research Group
Computer Science and Math Division
Oak Ridge National Labor
The following simple test code will exercise the following:
start_pes()
shmalloc()
shmem_int_get()
shmem_int_put()
shmem_barrier_all()
To compile:
shmemcc test_shmem.c -o test_shmem
To launch:
shmemrun -np 2 test_shmem
or for those who prefer to launch with SLURM
srun -n 2 test_shm
*** THIS RFC INCLUDES A MINOR CHANGE TO THE MPI-RTE INTERFACE ***
Note: during the course of this work, it was necessary to completely separate
the MPI and RTE progress engines. There were multiple places in the MPI layer
where ORTE_WAIT_FOR_COMPLETION was being used. A new OMPI_WAIT_FOR_COMPLET
Can you point me to a test program that would exercise it? I'd like to give it
a try first.
I'm okay with on by default as it builds its own separate library, and with the
RFC
On Aug 14, 2013, at 2:03 PM, "Barrett, Brian W" wrote:
> Josh -
>
> In general, I don't have a strong opinion of whe
Josh -
In general, I don't have a strong opinion of whether OpenSHMEM is on by
default or not. It might cause unexpected behavior for some users (like
on Crays, where one should really use Cray's SHMEM), but maybe it's better
on other platforms.
I also would have no objection to the RFC, provide
Ralph, and Brian
Thanks a bunch for taking the time to review this. It is extremely helpful. Let
me comment of the building of OSHMEM and solicit some feedback from you guys
(along with the rest of the community.) Originally we had planned to enable
OSHMEM to build only if '--with-oshmem' flag
Hi, Chris
Sorry for the delayed response. After much effort, the Open MPI 1.7 branch now
supports PMI2 (in general, not just for ALPS) and has been tested and evaluated
at small-ish scale (up to 512 ranks) with SLURM 2.6. We need to test this at
larger scale and plan to do so in the coming week
10 matches
Mail list logo
