svn commit: r326169 - in head: . contrib/ofed lib/libc/locale share/mk sys/amd64/amd64 sys/amd64/conf sys/conf sys/contrib/rdma/krping sys/dev/cxgbe sys/dev/cxgbe/common sys/dev/cxgbe/iw_cxgbe sys/...

[Mark Johnston]

On Fri, Nov 24, 2017 at 06:29:25PM +0100, Hans Petter Selasky wrote:
> On 11/24/17 18:22, Mark Johnston wrote:
> > On Fri, Nov 24, 2017 at 06:09:25PM +0100, Hans Petter Selasky wrote:
> >> On 11/24/17 16:00, Mark Johnston wrote:
> >>> Are there non-trivial interoperability issues between mthca and the
> >>> updated OFED stack? If so, could you describe them? If not, I would
> >>> strongly prefer to retain the mthca driver, as Isilon still has plenty
> >>> of hardware making use of it.
> >>
> >> Hi,
> >>
> >> There are no technical reasons except Mellanox hasn't focused on the
> >> mthca driver in this upgrade. With little effort you should be able to
> >> pull libmthca and the mthca driver from the mentioned sources and make
> >> it work.
> > 
> > In that case, could we please bring it back in to svn? It seems silly to
> > remove a driver just because it's not being actively maintained: that
> > isn't the bar for keeping drivers in FreeBSD, and I note that mthca is
> > still present in Linux. If there is some work needed to get the kernel
> > and userland components to compile again, I'm happy to do it; I just
> > don't want to have to maintain an out-of-tree HCA driver when there's no
> > good reason it can't stay in svn.
> > 
> 
> Sure, but we probably want to put it into sys/dev/mthca instead of 
> sys/ofed/xxx .

Ok.

> Are you saying you want to pull it in yourself and make 
> it compile?

I don't really *want* to, but I will if you don't. :)