>> I think so. I'm not sure of the best approach. With these patches, >> the qkey seems to be the one thing blocking the rdma_cm from >> supporting any IB UD application. > >Right.. qkey is kinda a funny thing, and pkey too I suppose. > >I'm not sure, I don't really know the usage model for qkey..
After a little more thought, I'm leaning toward keeping the qkey out of sockaddr_ib, and instead keeping it closer tied with the qpn. There's a 32-bit reserved field in struct rdma_ucm_conn_param that could carry it when resolving UD QPs. I will update the patches to handle this. Multicast is a little more difficult. The user lacks the ability to fully specify the MCMemberRecord. I can at least add the qkey to the new struct rdma_ucm_join_mcast definition. Plus, I guess we can always define sockaddr_ib_mc with whatever additional information we may want to add. Any thoughts on this? - Sean -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
