On Wed, Nov 30, 2016 at 06:17:34PM +0000, Hefty, Sean wrote: > > > Maybe the solution is to make the protocol selection explicit > > > throughout the APIs and associate it with a QP, rather than > > > attempting to list all transport protocols that a port can support. > > > > AH's are linked to a PD, not a QP.. > > But protocols are associated with QPs. I'm not sure *why* an AH is > linked to a PD. Conceptually the association seems unnecessary. The AH has to be linked to the PD because the PD specifies the hardware target and the AH is a hardware object. All objects must be traced back to a PD. It is linked to a PD not a QP because the AH can be shared across all QPs, which is useful for UD applications.. The AH is really similar to the ethernet layer in an IP stack, and the QP is akin the TCP layer. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
