On Tue, Jun 28, 2016 at 05:52:13PM +0200, Knut Omang wrote:
> On Tue, 2016-06-28 at 08:02 +0300, Leon Romanovsky wrote:
> > On Mon, Jun 27, 2016 at 12:17:58PM -0600, Jason Gunthorpe wrote:
> > > Doug and I have both stated we don't want to see so many
> > > single-provider APIs and churn in libibverbs. This was designed to
> > > be
> > > a generic API that all providers can implement.
> > > 
> > > The responsibility falls on you to make sure that it works
> > > universally. Compat is one option.
> > > 
> > > This is also why it is necessary to get the other provider authors
> > > to
> > > say this works on their hardware, because they *all* ultimately
> > > have
> > > to implement it.
> > > 
> > > I don't think many people realize this yet.
> > > 
> > 
> > Jason,
> > You are over-estimating the number of other providers who are
> > interesting in libibverbs in 2014-2016.
> > 
> > According to git log [1] in these years, I see only one major
> > contributor to this library.
> 
> I appreciate Jason's concern for other providers, I can assure we both
> use libibverbs for the new Oracle HCAs and also have changes/fixes to
> it. I want to get them out here, just a matter of getting enough time
> set aside to catch up (with the recent churn on both sides of the
> kernel/user boundary)

It is great and we all be happy to see more players in that field.
However it is not enough to use this library, Jason wants to see commitment
from other vendors to be ready to implement new proposed features.

> 
> > [1] https://git.kernel.org/cgit/libs/infiniband/libibverbs.git/log/
> 
> Thanks,
> 
> Knut
> 
> -- 
> Knut Omang, Ph.D
> Principal Software Engineer
> Oracle NSN Europe Design Center
> 
> 
>