Hefty, Sean <[email protected]> wrote: > I don't know if user space can allocate raw qps, but to be safe, I'll add XRC > INI and TGT > QP types after IB_QPT_RAW_ETHERTYPE (values 7 and 8) and adjust ibverbs to > make the mapping simple. What I was trying to suggest in my other email is > for OFA to > do something like this going forward: > enum ib_qp_type { > upstream values... , > IB_QPT_OFA_SPECIFIC = 2 << 24, > IB_QPT_OFA_XRC, > IB_QPT_OFA_RAW_PACKET > So, we don't end up with conflicting types, and OFA can treat OFA_XRC > differently if > the accepted XRC patches end up being different. (Of course, it's too late > to fix OFA > XRC this way, but maybe it's possible for OFA to support existing apps with > only a > recompile?)
I can't speak on behalf of XRC consumers, but as for the ethernet packet qp, we don't want to have two qp types, upstream one and ofa one. If it doesn't work for upstream to reserve the value of 8 for the packet qp (hopefully to be reviewed and merged soon...) we'll require everyone to recompile. Or. -- 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
