>Does this early association with the port space have any effect? Doing it early versus later - no. Doing it at all - yes.
>I would be inclined to ditch the port space concept entirely for >AF_IB. Just ignore the input parameter and always base the selection >on the SID region. It is confusing to that there are two ways to >specify the same thing. The address family is not sufficient to determine the desired port space. For example, AF_INET is usable for RDMA_PS_TCP and RDMA_PS_UDP. >Is there any reason the port space has to be known when the cm_id is >created but before bind? No - but it is still required for transport neutrality. rdma_create_id() simply stores the value. So... the port space could be specified during rdma_bind_addr and rdma_resolve_addr instead of rdma_create_id, with the port space being determined based on the sid/mask if AF_IB, rather than given directly. That seems more complex to me than just specifying it up front when rdma_create_id is called. -- 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
