From owner-freebsd-arch@freebsd.org Sat Mar 17 20:03:48 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 036A2F64F74; Sat, 17 Mar 2018 20:03:48 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E9376C3DB; Sat, 17 Mar 2018 20:03:47 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 98064260370; Sat, 17 Mar 2018 21:03:45 +0100 (CET) Subject: Re: [HEADS UP] - OFED/RDMA stack update To: Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , Meny Yossefi , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch References: <1519683699.47932.5.camel@FreeBSD.org> <20180226224311.GT94212@kib.kiev.ua> <3027f48e-0ba8-555d-df23-d638303cb125@selasky.org> <20180317195200.GA5223@ox> From: Hans Petter Selasky Message-ID: <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> Date: Sat, 17 Mar 2018 21:03:40 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180317195200.GA5223@ox> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2018 20:03:48 -0000 On 03/17/18 20:52, Navdeep Parhar wrote: > Hold your horses. Do you have confirmation from the affected party that > the shims are adequate for them? I have been waiting for that before > looking at this branch. Hi Navdeep, Mellanox has received an API list from at least one party, and has taken the action to support all the required APIs. > Is the iw_cxgbe breakage a simple merge conflict as previously discussed > or do the shims require driver changes? It is a merge conflict. The code already compiles in 12-current. > If they don't then it should be > possible to drop the iw_cxgbe from head into this branch and it should > just work, is that correct? Yes, it shouldn't be too hard to do and I would appreciate if Chelsio could throw some resources at this ASAP. I believe the new code will benefit everyone using Infiniband/RoCE and iWarp with FreeBSD. --HPS