From owner-freebsd-arch@freebsd.org Tue Mar 20 20:07:39 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 0C792F6A19E; Tue, 20 Mar 2018 20:07:39 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 74B0A84990; Tue, 20 Mar 2018 20:07:38 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id 139so5905065wmn.2; Tue, 20 Mar 2018 13:07:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ywvAj3LCHifFGTMLaNs1klcykTEygXtTk9Zy1scKsb0=; b=Nz7I1mM2HGIs4GoDb+B+WJ+nDHlNbj2PZ6Xe9dbwgkgqCqXmFLBjuTFll/sODISpzo mnEaOvcnWIeB2YN5abuSZy3dRGQrXFZYIr1bTWEarzk+sZpzUgkVD8tV0QDub1/CwoKR KxlNppdEpWLQUber2UqKCsPrlwwwdDVvkS5Iqp0bRxZWvtas0iOBsgi/a3qembsOosC9 SXCZBSSiyFuZKGa5OCCGCXLTqF/zl3UrfWtjowC+zicCe3rbFNX/1A6PYQzFmdwwYEQT pSxWG+slg38+tOV+lEDN5kyEbBeYktJXQuFazN23cif/QP3Kzw+5/U0esIp4ejMxlrmo mUew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ywvAj3LCHifFGTMLaNs1klcykTEygXtTk9Zy1scKsb0=; b=lak5ZatNMEGsenUzaj5MyzKeBVl3NKMIouQ/lyBuDD2QuO0PeZbF+9FNqx2QiUXGwB yoXwFK5gqZ03z5qjtP8p32zI4xTV19zYudPY5eRdRGzQTYsmyaUZAqi9GsFPE0oHEWyO OK4H9zXZHw8euAMBlcgisv49xHjUHIOJSocFSN2XqZRy7lxlIHKlCGchs3qTtNrc6RFg UHBkhFhs0LObJVeGZNS3T7njMZO0DFaBgM0DFY4wDVv48XK6O/KBM0FuFmlSCxFhK2SS 7mQh8qV0onzCSgh9CVyHbrsrlJ7QbcOAP82pxsvNiGTKXy9hQfWaGdVfbdRkpilwQP87 HyLw== X-Gm-Message-State: AElRT7FUOFxPTm+zprc7+OhZPbV5lKPJkZF3zA6DL4eBhyV62fKT9Ic0 c8fGaul0eApcZUcicW+4zAPWC4UI X-Google-Smtp-Source: AG47ELttX7eIIsLhiKTgOGfJa47jB6mez5SWLkW2/UYJaKKWMS2ukRubdUA2p21/orkaYhisPSm/zA== X-Received: by 10.28.134.5 with SMTP id i5mr655895wmd.127.1521576456967; Tue, 20 Mar 2018 13:07:36 -0700 (PDT) Received: from [10.192.166.0] (stargate.chelsio.com. [12.32.117.8]) by smtp.googlemail.com with ESMTPSA id m35sm5358804wrm.59.2018.03.20.13.07.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 13:07:36 -0700 (PDT) Sender: Navdeep Parhar Subject: Re: [HEADS UP] - OFED/RDMA stack update To: Hans Petter Selasky , 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> <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> From: Navdeep Parhar Message-ID: <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> Date: Tue, 20 Mar 2018 13:07:31 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable 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: Tue, 20 Mar 2018 20:07:39 -0000 On 03/17/2018 13:03, Hans Petter Selasky wrote: > On 03/17/18 20:52, Navdeep Parhar wrote: >> Hold your horses.=C2=A0 Do you have confirmation from the affected par= ty that >> the shims are adequate for them?=C2=A0 I have been waiting for that be= fore >> looking at this branch. >=20 > Hi Navdeep, >=20 > Mellanox has received an API list from at least one party, and has take= n > the action to support all the required APIs. >=20 >> Is the iw_cxgbe breakage a simple merge conflict as previously discuss= ed >> or do the shims require driver changes?=C2=A0=20 >=20 > It is a merge conflict. The code already compiles in 12-current. I tried backing out r329391 and r329017 in a local copy and then was able to merge r320418, r323082, and r326169 in that order without any conflicts. But iw_cxgbe/cm.c still doesn't compile in the projects branch because it has some socket code that relies on some of glebius's changes available only in head (I checked with him and they aren't MFC'able). I'm trying to figure out what to do about those. And what about the cxgb breakage? Is there any simple way to make an old style driver work with the new stack? T3 iw_cxgb in head was retired before the ofed overhaul. Regards, Navdeep