I see the problem. Yoda is directly calling bml_get without first checking to
see if the bml_btl supports rdma operations. If you only have the tcp btl, then
rdma isn't supported, the bml_get function is NULL, and you segfault.
What you need to do is check for rdma, and then fall back to message
Maybe this is a stupid question, but in this case (I believe this goes all the
way back to our initial discussion on OSHMEM), how does one fall back onto
send/recv semantics when the call is made at the SHMEM level to do a put? If a
BTL doesn't support RDMA, then it doesn't seem reasonable to ex
You can always implement a put/get using send/recv semantics. The performance
drops, but the functionality is the same - after all, it's still nothing but
data movement, and ultimately the application doesn't care how the data got
there.
For a first-cut, you can certainly do a clean abort if rd
On Aug 15, 2013, at 18:06 , Joshua Ladd wrote:
> Maybe this is a stupid question, but in this case (I believe this goes all
> the way back to our initial discussion on OSHMEM), how does one fall back
> onto send/recv semantics when the call is made at the SHMEM level to do a put?
The same way
On 8/15/13 10:30 AM, "George Bosilca" wrote:
>
>On Aug 15, 2013, at 18:06 , Joshua Ladd wrote:
>
>> Maybe this is a stupid question, but in this case (I believe this goes
>>all the way back to our initial discussion on OSHMEM), how does one fall
>>back onto send/recv semantics when the call is m
