Date: Fri, 24 Nov 2017 18:34:02 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Mark Johnston <markj@FreeBSD.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: 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/... Message-ID: <4695efa6-c8d5-e860-3c9b-939ac4b91abc@selasky.org> In-Reply-To: <20171124173512.GB1098@raichu> References: <201711241450.vAOEoSFW056744@repo.freebsd.org> <20171124150044.GA94025@raichu> <cd57ba80-9a38-9daa-6eab-4329de2f3a70@selasky.org> <20171124172239.GA1098@raichu> <5404fdf3-59f0-7bb0-772e-a9003671b0ef@selasky.org> <20171124173512.GB1098@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/24/17 18:35, Mark Johnston wrote: > 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. :) > Let me discuss this at Mellanox first. I'll get back to you on Monday on this topic. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4695efa6-c8d5-e860-3c9b-939ac4b91abc>