Re: Different signatures to ibv_open_xrcd - branch issue?

[Shlomo Pongratz <shlomop-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>]

On 3/25/2013 6:35 PM, Hefty, Sean wrote:
>> In libibverbs/include/infiniband/verbs.h the API "ibv_open_xrcd" is
>> defined with the following signature;
>> static inline struct ibv_xrcd *
>> ibv_open_xrcd(struct ibv_context *context, struct ibv_xrcd_init_attr
>> *xrcd_init_attr)
>> And libibverbs/examples/xsrq_pingpong.c the call is O.K. however in
>> librdmacm/examples/rdma_xserver.c I see a different call sequence i.e.
>> "attr.ext.xrc.xrcd = ibv_open_xrcd(srq_id->verbs, -1, 0);"
>> My git branch for libivvers is based on origin/xrc2 and for librdmacm is
>> based on origin/xrc.
>>
>> Is any of my branches wrong?
> The librdmacm changes are against an older version of the changes.  The libibverbs has the correct API, which incorporates the extension mechanism that's been discussed.  Once libibverbs has been accepted, the librdmacm can be updated.  (The librdmacm code is surrounded by a #define, which disables it from the build.)
>
> - Sean
I understand that currently I can't do RDMA using XRC, is that the case?
How complicated are the required modifications needed to make librdmacm 
complies to the libibverbs changes?



--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html