[libfabric-users] 2 questions

[Biddiscombe, John A.]

Question 1: I’ve created a passive endpoint (on both of two nodes) for listening, exchanged name details and created an active endpoint (on one node) that I call connect on, giving the address details of the other node where the passive endpoint is listening.

I’m getting “ret=-22 (Invalid argument)” on my call to connect – since there are only 2 arguments set in the call I’m using
            ret = fi_connect(ct.ep, name_data, NULL, 0);

dumping out the 16 bytes of buffer used for name (ip address is 192.168.3.36:
2:0:227:27:192:168:3:38:0:0:0:0:0:0:0:0:

enabling logging shows

libfabric:verbs:core:fi_ibv_msg_ep_connect():151<info> src_addr: 192.168.3.36:36996
libfabric:verbs:core:fi_ibv_msg_ep_connect():158<info> dst_addr: 0.0.0.0:0
fi_connect(): /users/biddisco/src/hvtkm/hpx/plugins/parcelport/libfabric/libfabric_controller.hpp:667 , ret=-22 (Invalid argument)

What might be wrong? (the ping pong example is just the same, the only difference is I have a passive endpoint and an active one on the same node – I’m using the same fi_fabric/fi_domain for both –could that be what’s wrong?)

Question 2 : If I register a buffer for send/recv/read/write/etc and split it into N smaller buffers, in the post_ send/recv calls, there does not seem to be a way of using an offset into the buffer so that I can post N of them each with a different offset (c.f. verbs equivalent, which uses the same local key, but a different offset for each).
Can I do that, or do I have to register the buffer as a vetor of smaller buffers and ive each one a descriptor individually?

Thanks

JB


--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/libfabric-users/attachments/20170220/0a5d1d99/attachment.html>