On Wed, Nov 30, 2016 at 04:30:09PM +0000, Liran Liss wrote: > > I'd love to see any such device support protocol choice per connection, not just > > per port. That of course would have implications on the rdma commection > > manager api. > Exactly. If/when such devices appear, we would need to extend > connection management to specify the protocol, rather than infer it > from the port space. We support that perfectly today as long as the port creates two 'struct ib_devices'. Anything else will require some kind of changes to libibverb's API to specify the AH style. > Rethinking about the uAPI, maybe we should report a protocol > bit-mask similar to the kernel's, instead of QP types? This would > provide all the required information (e.g., any combination of > RoCEv1/v2, iWARP, and Raw Ethernet for Ethernet links) for today's > use-cases as well as tomorrow's combined RoCE/iWARP devices. Maybe we should dump this uapi stuff until Matan's patches are done. The introspection possible with Matan's work is flexible enough to cope with more cases.. 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
