RE: [PATCH 26/26] rdma/ucm: allow user space to specify AF_IB when joining multicast

Sean Hefty
2010-04-01T23:10:02Z

>Humm, interesting.. So you propose to accept addresses for families
>other than the one used to create the cm_id?
>
>Just from a simplicity of the future perspective I'd say not to bother

Part of the reasoning behind the existing code is that users requested the
ability to join a multicast group using an address of 0, so the transport could
select what the address. Once the address was selected, it was communicated to
remote peers, who would join using the assigned address. Today, the assigned
address is passed as AF_INET6. This patch tries to 'fix' that and allow the
address to be passed to the kernel as AF_IB instead.

For compatibility reasons, I think we want to continue to support AF_INET
rdma_cm_id's using AF_INET6 or AF_IB. Off the top of my head, I can't think of
any reason why support for AF_IB id's would need AF_INET/AF_INET6. I don't know
if IBoE would want this or not, but I can update the patch to remove this
support.

- Sean