Yeah, that will be a problem. We made large changes to the BTL interface
with v2.x. If your customer requires a version that works with v1.10 I
suggest looking that the usnic btl to see how it might be possible to
write a btl that supports both the new and the old interface. You can
also use an ol
Hello Nathan, Mike and all
Thank you for your responses. Let me rephrase them to make sure I
understood them correctly, and please correct me if I didn't:
1. Atomics are (have been) used in OSHMEM in the current (v1) release
2. They are (will be) used in the MPI RMA in v2 release, which has not
h
On Thu, Mar 03, 2016 at 05:26:45PM -0500, dpchoudh . wrote:
>Hello all
>
>Here is a 101 level question:
>
>OpenMPI supports many transports, out of the box, and can be extended to
>support those which it does not. Some of these transports, such as
>infiniband, provide hardwar
Hi,
Please check shmem.h for exposed API for hw atomics, and memory put/get
operations.
OMPI has plugin system, where every transport can expose what operations
are supported and OMPI will pick one which does for user-called API
requiring it.
For hw which does not support hw atomics or remote memo
Hello all
Here is a 101 level question:
OpenMPI supports many transports, out of the box, and can be extended to
support those which it does not. Some of these transports, such as
infiniband, provide hardware atomic operations on remote memory, whereas
others, such as iWARP, do not.
My question
