No problem,
expanded it is.
>can we do this so that the new verb lies after XRC in ib_context, since OFED
>1.3 went out
>with XRC in userspace (so we don't break binary compatibility):
>
>struct ibv_context {
> struct ibv_device *device;
> struct ibv_context_ops ops;
> int cmd_fd;
> int async_fd;
> int num_comp_vectors;
> pthread_mutex_t mutex;
> void *abi_compat;
> struct ibv_xrc_ops *xrc_ops;
> /* ==> new verb ops structure pointer here */
>};
I'm going to release some patches, based on your XRC patches, in which
I'm going to replace xrc_ops with more_ops.
These patches will will be relative to your patches.
I hope it's ok with you.
Ron
On Thu, Jul 10, 2008 at 10:39 AM, Jack Morgenstein
<[EMAIL PROTECTED]> wrote:
> On Tuesday 08 July 2008 16:33, Or Gerlitz wrote:
>> Assuming this solution (a create-qp-extended verb that gets also
>> creation flags) would be the one implemented at libibverbs, are you fine
>> with applying the same approach to librdmacm that is adding a matching
>> call eg rdma-create-qp-extended that just calls the new verb?
>
> Please use "expanded", not "extended", to avoid any confusion with
> XRC (Extended RC) qp's.
>
> - Jack
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
>
> To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
>
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
