From owner-svn-src-all@freebsd.org Fri Nov 24 17:22:45 2017 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0CDADEC935; Fri, 24 Nov 2017 17:22:45 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62C437CB39; Fri, 24 Nov 2017 17:22:45 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-it0-x242.google.com with SMTP id b5so14113392itc.3; Fri, 24 Nov 2017 09:22:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=0RU2lkG+Tls9t9HNdlsowSONTCqg1vLqfVaSgT7LoVA=; b=SLmaHUYtC4cNHWGVpU+YYOP0YujSGQm7HKCGKYz4Htk+nOsyP0kiXyze5cyW0kFy9x E/ynKb6gUEQDbifjZ049WyFnyv28iFIjGM1hR+JOuyD6c8veD/Y6+pQN9TMgcRrcW544 fKYsDJ/ErgQF0pRYZuLaY3bmHJRjwEaZtBxaZka29h6NhP3vpj6nAKfhVCu4kHCX+WW4 DNcouQSExEJ6Yd+RlCabqP1Z9D+yMP7DsvYVbycIFKYH/vnkNTm6u8A3F2jPe2sz29sq 983QOV50TgdW74PtETBPxd36t6FD7UuW6Tt0fimUW6/TXEgvDYLuYgPIQRxtsXrw1CLl QP0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=0RU2lkG+Tls9t9HNdlsowSONTCqg1vLqfVaSgT7LoVA=; b=HfC1NdfTQ05a9zVW+Jxm5l0TuCXuVA9YxmlDtbI4QlkQXCKOccafoo10nrHdbJbY+A 7rGZlWdcqgjMvQKVw7F0Qo48Nir8MlXxJwp8oqvZ1M9RXmb2+16Tlf+D8AxbGmIvu5/s EGDHIpsMXK1joS5WPobq6Cf9LUm6NzwVeSpM5fMPDdQV9HCokGt/jQ4ioqRXdV+nh/Cu A7j+rteKD2kWUAZzXWFgZMvtI0M9hAptF07xt+O9vh78AU3c5cEW7pt+tBRTtyjeB6zf TM7m3q8ND/I0kCMwoIN3L5iRJUncC5JFb0kVN5eDRQDr9/H6h60AA38iaxPy1ISgJiSg w6tw== X-Gm-Message-State: AJaThX4n6N5rrndYVOTZtM0vGN+qO6c5zWBxkrt+49x9QrnuMl8f6n/F OME/Yp1mu1zLpMkzQIbRztGJOg== X-Google-Smtp-Source: AGs4zMZ+n9UglXqBcmKM9oc857nryMtGd0DdDxh1Sq2+ZFhkB5ws/bbOT2p7iSxoYe5WUkw4/zSD2g== X-Received: by 10.36.145.1 with SMTP id i1mr16719539ite.122.1511544164700; Fri, 24 Nov 2017 09:22:44 -0800 (PST) Received: from raichu (toroon0560w-lp140-01-69-159-38-22.dsl.bell.ca. [69.159.38.22]) by smtp.gmail.com with ESMTPSA id z188sm4524842itb.28.2017.11.24.09.22.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Nov 2017 09:22:43 -0800 (PST) Sender: Mark Johnston Date: Fri, 24 Nov 2017 12:22:39 -0500 From: Mark Johnston To: Hans Petter Selasky 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: <20171124172239.GA1098@raichu> References: <201711241450.vAOEoSFW056744@repo.freebsd.org> <20171124150044.GA94025@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 17:22:45 -0000 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.