munication will fail, because the proc lookup will fail
inside the BTL. If the MPI layer doesn't call add_procs(), someone else
has to. In this case, that someone else is the OpenSHMEM layer.
Brian
On 1/15/14 7:45 AM, "Igor Ivanov" wrote:
Brian,
Sorry for slow reaction.
I am n
ML to initialize the procs arrays for the BTLs.
Brian
On 12/23/13 3:49 AM, "Igor Ivanov" wrote:
Brian,
Could you look at patch based on your suggestion. It resolves the issue
with mca variable.
Igor
On 18.12.2013 01:48, Barrett, Brian W wrote:
The proposed solution at the bottom i
lf Of Nathan Hjelm
Sent: Monday, December 16, 2013 12:44 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] bug in mca framework?
On Mon, Dec 16, 2013 at 05:21:05PM +, Joshua Ladd wrote:
After speaking with Igor Ivanov about this this morning, he summarized
his findings as follows:
1. Valgri
On 04.12.2013 17:56, Jeff Squyres (jsquyres) wrote:
On Dec 4, 2013, at 2:52 AM, Igor Ivanov wrote:
It is the first mca variable with type as string from btl/openib as
'device_param_files'. Actually you can disable it and get failure on the second.
Description of case we see:
1.
It is the first mca variable with type as string from btl/openib as
'device_param_files'. Actually you can disable it and get failure on the
second.
Description of case we see:
1. openib mca variables are registered during startup as stage at select
component phase;
2. but a winner is cm compo
Hi Jeff,
I would like to add few notes inline
Igor
On 25.10.2013 20:33, Jeff Squyres (jsquyres) wrote:
We had a few emails a little while ago, and decided that the branding should be
"oshmem" because Open SHMEM is different than (original) SHMEM.
I notice that there's still:
- shmemcc / shm
,
Cray`s etc products.
SIte www.shmem.org says that "The SHMEM™ Application Programming
Interface (API) definition and the SHMEM trademark are the property of
SGI. "
Igor
On 18.10.2013 16:33, Jeff Squyres (jsquyres) wrote:
On Oct 18, 2013, at 1:18 AM, Igor Ivanov wrote:
Is th
Hi Jeff,
Is there naming convention related configure options in OMPI?
Do you see any objections about --enable-oshmem-xxx or they must be
replaced with --enable-shmem-xxx?
Regards,
Igor
On 17.10.2013 14:20, Jeff Squyres (jsquyres) wrote:
Mellanox --
In r29448, you deleted the comment witho
