Jason wrote, >I was commenting specifically on the idea that we'd ever release a libverbs >that forced a kernel upgrade. I hope we all agree that is not acceptable.
This means that user-space and kernel space packages can be released on separate schedules, so there is no need to tie the two together. That is good. >IMHO - we should be talking about getting to the point where we can deliver >the kernel rc and uapi rc together to someplace like UNH and vendor internal >labs and >expect them to test that pair. Regularly, ideally on the kernel >release time line. I am all for doing more testing earlier, but I am not sure that people (like UNH and the vendor validation teams will sign up to do it. This would essentially double their testing effort (and costs), first testing the user-space packages with the upstream kernel that is under development, but also still having to test what comes out of the distro or OFED. This is because it is what is in OFED and/or the distro that their customers will actually run. Very few customers actually run the kernel.org kernel, they run what is in the distro. And BTW, UNH gets paid to do testing, so someone would have to cough up the $$ to get them to add this additional testing. So it all really comes down to resources and cost and being able to justify that doing more testing of upstream code is worth it. -- 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
