On Fri, Jan 27, 2017 at 09:32:51AM -0500, Doug Ledford wrote: > On 1/26/2017 8:17 PM, Hefty, Sean wrote: > >> - Ship libibverbs.rpm with the updated driver and matched libibverbs > >> This is pretty easy, I probably would recommend this. > > > > This has issues if there are multiple providers present. Maybe > > that doesn't happen in non-testing environments. I wonder if the > > distros would agree with this approach. > > I don't know how much I would rely on the belief that mixed environments > don't happen outside of testing. Yes, I've heard many complaints in production in this area. As it stands today the changes to libibverbs in vendor trees are too extensive, the only way to resolve them is to merge the vendors patches into one source tree and build a custom release. I think rdma-core will make that much simpler. Making the ABI private or public doesn't really help things either way, as far as I can tell. Remember the stable ABI is upstream, not in a vendor tree, so don't expect a random vendor libibverbs to work with any other providers, even today! They might link, but based on what I've seen they will be subtly broken. Ideally vendors will get their stuff upstream and a site could choose to just use upstream rdma-core instead of a vendor tree. I would still suggest vendors shipping libibverbs.rpm as their update is and reasonable and easy approach for their simple users. 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
