On Thu, Oct 13, 2016 at 07:43:25PM +0000, Hefty, Sean wrote: > > What makes OFVWG more qualified to review an ABI than linux-rdma? > > We've had this discussion on the list before. The issue is that > verbs isn't just a software API. It defines a hardware > implementation. The consensus was that some 'standards' body needed > to be able to review the proposed changes and its impact. The OFVWG > was selected as the best available option. If we want to say no, > and let the linux-rdma maintainer dictate the hardware interface > exported by the kernel, then, yes, that's an option. A bigger objection I have is that much of this new stuff is not adaquately documented. Tag matching is a great example. It looks like this introduces many new headers into the on-wire protocol. Where are these headers documented? Where is the spec for the on-wire format? Where is the implementation for rxe? Basically, is there enough public information that another vendor could implement this wire protocol? (if not, why are we even *contemplating* merging something like this???) 'Hopefully' the answer is that this information is all hidden away in the IBTA... Which opens up an entire new line of problems reviewing something like this without seeing the agreed spec.. The basic problem with linux-rdma is that it is not a reasonable place to review a new on-wire protocol amendment to the IBA. Nor is ofvwg for that matter. 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
