>Could you elaborate a bit on how you are mixing the port space and the >SID?
The SID is divided into multiple, disjoint regions. (Annex 3 defines some of the regions.) The port space selects a specific region. >IMHO, after thinking about it for a bit, I would prefer to see the >port space be unused from a user-space perspective when used with >AF_IB. The rdma_cm_id is associated with a port space on creation, before it's known what address family will be used. The kernel code enforces that the SID is formatted correctly for the port space that was selected. >If a ps is needed in the kernel then it should pick the ps based on >the SID prefix that user space provided.. I guess prior to adding the >mask bits this wouldn't have made sense, but now that they are in it >seems like the way to go. I added sib_mask to sockaddr_ib, but it's unused at this point. I think what you're saying makes sense, but for RDMA_PS_IB, once it's defined. RDMA_PS_IB may need to behave as RDMA_PS_TCP or RDMA_PS_UDP based on the sib_mask and SID, and ensure that any selected SID is reserved from the correct underlying SID region. Does this make sense? - 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
