From owner-freebsd-arch@freebsd.org Sun Mar 18 22:56:31 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 137ECF5B7EF; Sun, 18 Mar 2018 22:56:31 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 845006BCB0; Sun, 18 Mar 2018 22:56:30 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-pf0-x22a.google.com with SMTP id l27so1767300pfk.12; Sun, 18 Mar 2018 15:56:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=R3QymJFMYYCJNVx+1+ozGcEEsLaOB5/dMmH+5mVvIts=; b=NJgUOPcm2YzRYH3H5RoF6v7toWPQl9w3P9tbc4zOeWFKb4ZmpJtrglt1SNbWjoMkRX 5eAiaJDbsWpIuMhF5m4Vqc99RBdy5HtJ16LbWBhSaJjzYNkDx/XYUwihnn2Jv2PLJ28r Lh730dZ7c2M4ESfqyo+7Q+yMVFLas63Jovm+r4xNYJ1UuYYdx8xXmjQ/AXjmunRDiLWy q4kGo7GaIhNmQ+kpmGVbfq2V+1V40bSJTPA7YQa27DKk5huzpE13GHrgJiPCnk4O100+ mM8+NDrHbo9o5c/7at1T/QjQAzsjf58PI+jrviduC5Nb1kkyWUBqr4jZOonTQu+zM91P JdiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=R3QymJFMYYCJNVx+1+ozGcEEsLaOB5/dMmH+5mVvIts=; b=U4/sh5jsvusAPMmAdJnCMCCfOuY5PvCw1aWDgBBoDUOmoHIz8+ooBrzk2S2z1tAhuc 4Vz2FOJZdHsRJaF3NPvr/Perx5NmlnK+QI6Tr1oCOEVfip9+wWTj7JT09FvtHvjnLogt bv3l+31pQFlqQ88pD4pKeCYqnPV0BiaKzfQTuSMyR2PPnu41XnV5zBCBwZBd4Ivk46Z7 mnzf+2X8+aXZ3jcV3WwZyFi/V9X2kmmL+6iEK+VAdj7ida55WfG4Q83DIdax8t2G+Xj0 iltQBgLia97xbClZMhQq2pjg5gJs/4GQ0qnIRaW6Lkk4eQDUwusu4TkdpSTBQ603xZxM au2g== X-Gm-Message-State: AElRT7FKEEwTPDjJqfXV1j/VhSpd1HMmuyeuS/R5+9uCkRY4oWQraZNj S/XBmrCAuLB6DIdFC4YYxrM0j01G X-Google-Smtp-Source: AG47ELvSuhOGiJmhqDBJQgwPo1kz2jYQl6vEYbA4/63RfwWyhbaOhFtLWg3S7KWr3BiDBUScF2FIMw== X-Received: by 10.101.70.203 with SMTP id n11mr7566419pgr.166.1521413789580; Sun, 18 Mar 2018 15:56:29 -0700 (PDT) Received: from ox ([2601:641:c000:b800:d4a0:ba9e:80e:6a83]) by smtp.gmail.com with ESMTPSA id p86sm26952670pfi.55.2018.03.18.15.56.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Mar 2018 15:56:28 -0700 (PDT) Date: Sun, 18 Mar 2018 15:56:19 -0700 From: Navdeep Parhar To: Hans Petter Selasky Cc: Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , Meny Yossefi , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch Subject: Re: [HEADS UP] - OFED/RDMA stack update Message-ID: <20180318225619.GA6132@ox> Mail-Followup-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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6d451a3b-a635-08b1-f8d4-52fdc48083d6@selasky.org> User-Agent: Mutt/1.5.24 (2015-08-30) 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: Sun, 18 Mar 2018 22:56:31 -0000 On Sat, Mar 17, 2018 at 09:03:40PM +0100, Hans Petter Selasky wrote: > 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. Ok that doesn't sound that bad. I'll take a look early this week. Regards, Navdeep > > >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 > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" 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 From owner-freebsd-arch@freebsd.org Tue Mar 20 20:15:11 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 BDA9BF6AB55; Tue, 20 Mar 2018 20:15:11 +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 588C3851AB; Tue, 20 Mar 2018 20:15:11 +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 DF0E4260186; Tue, 20 Mar 2018 21:15:09 +0100 (CET) Subject: Re: [HEADS UP] - OFED/RDMA stack update To: Navdeep Parhar , 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> <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> From: Hans Petter Selasky Message-ID: <8aa54a0d-feaa-0c0f-82e2-5d32c873375e@selasky.org> Date: Tue, 20 Mar 2018 21:15:03 +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: <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> 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: Tue, 20 Mar 2018 20:15:11 -0000 On 03/20/18 21:07, Navdeep Parhar wrote: > 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. Hi, The most simple way is to pull this driver from Linux 4.9, including libcxgb for user-space, if possible, though I'm not sure about the FreeBSD specific areas of iWarp and socket handling. I think you know that part better than I do. After pulling from Linux 4.9 you need to extend this change to cover the iw_cxgb: https://svnweb.freebsd.org/changeset/base/330508 Or can you retire iw_cxgb? --HPS From owner-freebsd-arch@freebsd.org Thu Mar 22 11:36:35 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 96CC6F5D0A7; Thu, 22 Mar 2018 11:36:35 +0000 (UTC) (envelope-from menyy@mellanox.com) Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0081.outbound.protection.outlook.com [104.47.2.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7BBC6F16B; Thu, 22 Mar 2018 11:36:34 +0000 (UTC) (envelope-from menyy@mellanox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=xSqSEk7bQzCSO9GCZEE7YUFP0SSSwMuhX1mjP0xuiXM=; b=BEgR3vl9wk6tvkwDcocXQXyEttaE82ERoVJAIBmTCpJpWP4aek61k1GBnqj2vouVj/txeGlWHToDiQD4VYpuIrvOAgJJ1CPrZZxQ76zzq1ERjur+DduNPjtoe0SH8o+k26KEsaTrQqlxDo8M8IGfBPbgB8Be58ixlffDLQsC0RI= Received: from VI1PR0501MB2863.eurprd05.prod.outlook.com (10.172.12.8) by VI1PR0501MB1949.eurprd05.prod.outlook.com (10.166.44.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.609.10; Thu, 22 Mar 2018 11:36:30 +0000 Received: from VI1PR0501MB2863.eurprd05.prod.outlook.com ([fe80::89b0:b1d8:fec6:c6ec]) by VI1PR0501MB2863.eurprd05.prod.outlook.com ([fe80::89b0:b1d8:fec6:c6ec%17]) with mapi id 15.20.0588.017; Thu, 22 Mar 2018 11:36:30 +0000 From: Meny Yossefi To: Navdeep Parhar , Hans Petter Selasky , Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , "'FreeBSD-stable@FreeBSD.org'" , freebsd-arch Subject: RE: [HEADS UP] - OFED/RDMA stack update Thread-Topic: [HEADS UP] - OFED/RDMA stack update Thread-Index: AdNZQQ/RuIbNiZgtQumqRm3gP9gf8RVzyJuwAA/+YIAAAMCGgAN8uZ6AADjXuwAAAGXsAACXAjyAAFI51uA= Date: Thu, 22 Mar 2018 11:36:30 +0000 Message-ID: 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> <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> In-Reply-To: <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=menyy@mellanox.com; x-originating-ip: [193.47.165.251] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; VI1PR0501MB1949; 7:Kgqx+KeBdP0T4GTiGJCDAJnI7Dm5jtmt9ltX29McXrKx/ipvJbcuiVwV5ayXaPAuNPm1qbLMsXuinxvndpvNZ7d7PckI1vDd06CEaj//AFp9RtnCtKtWahfS7u1jnYwl6MdiH+Bau3Sumhk/IvnC7qX8n7xzobU0175RukBfvb4T9VzgAG22NU+OCpDGgUiZL3tiI8h+5SzYFO3t4LGzAN617bvRevWR6VpK5vSQ0RFIze6wrHUlL9BjPRkXMfTo x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 6afe4e1a-28cd-472c-9552-08d58fe927fe x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR0501MB1949; x-ms-traffictypediagnostic: VI1PR0501MB1949: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(85827821059158)(5213294742642); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231221)(944501327)(52105095)(6055026)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:VI1PR0501MB1949; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0501MB1949; x-forefront-prvs: 0619D53754 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(39380400002)(396003)(366004)(39860400002)(13464003)(189003)(199004)(97736004)(305945005)(2950100002)(25786009)(74316002)(7736002)(5660300001)(76176011)(2906002)(2900100001)(3846002)(6116002)(7696005)(6436002)(55016002)(5250100002)(3280700002)(8936002)(3660700001)(8676002)(15650500001)(81166006)(81156014)(9686003)(33656002)(6246003)(99286004)(68736007)(105586002)(53936002)(110136005)(66066001)(229853002)(86362001)(106356001)(478600001)(26005)(93886005)(6506007)(102836004)(53546011)(59450400001)(446003)(316002)(186003)(14454004)(96633001)(491001); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0501MB1949; H:VI1PR0501MB2863.eurprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: h7hNxaHtGPsV81roG0+iMi+ZiMWHtanS5K3xLt5phxKkSuD4gcxv2iZRocXcBZD6OVQ9p7j5Pl/alaMHCWzWrqGMPObRbArdDpPJqoBeHieMyPkgL/j6bEbWNa8OteexQ8sipQVgpPDUaYquJoKQ7rBMmRPK3T8AygqHf2Sk9oEq/sxAA0WkYAtNiq7hjXFqEgMZemMVg28nPv1gM5xZLxXq+/1BuCuoj55lFF7SxClHUVit9SsHOYhO+Qx4++V9mJgVQjHbhG1YlE5eRxI4kNdSgW7y8h6zkBhHxgtFhRO6wzE5189Sck3iHQCJIv9rqMKUrBFnyLsmdCwnrXdVIw== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-Network-Message-Id: 6afe4e1a-28cd-472c-9552-08d58fe927fe X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2018 11:36:30.2222 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0501MB1949 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: Thu, 22 Mar 2018 11:36:35 -0000 SGkgTmF2ZGVlcCwgDQoNCldoYXQncyB0aGUgY3VycmVudCBpV0FSUCBzdGF0dXMgb24gdGhlIHBy b2plY3QgYnJhbmNoPyANCklmIGl0J3MgcmVhZHkgd2UnZCBsaWtlIHRvIG1lcmdlIGl0IHRvIEZy ZWVCU0QxMS1TVEFCTEUgaW1tZWRpYXRlbHkuIA0KDQotTWVueQ0KDQoNCi0tLS0tT3JpZ2luYWwg TWVzc2FnZS0tLS0tDQpGcm9tOiBOYXZkZWVwIFBhcmhhciBbbWFpbHRvOm5wYXJoYXJAZ21haWwu Y29tXSBPbiBCZWhhbGYgT2YgTmF2ZGVlcCBQYXJoYXINClNlbnQ6IFR1ZXNkYXksIE1hcmNoIDIw LCAyMDE4IDEwOjA4IFBNDQpUbzogSGFucyBQZXR0ZXIgU2VsYXNreSA8aHBzQHNlbGFza3kub3Jn PjsgS29uc3RhbnRpbiBCZWxvdXNvdiA8a2liQGZyZWVic2Qub3JnPjsgJ2ZyZWVic2QtaW5maW5p YmFuZEBmcmVlYnNkLm9yZycgPGZyZWVic2QtaW5maW5pYmFuZEBmcmVlYnNkLm9yZz47IGZyZWVi c2QtZHJpdmVycyA8ZnJlZWJzZC1kcml2ZXJzQG1lbGxhbm94LmNvbT47IE1lbnkgWW9zc2VmaSA8 bWVueXlAbWVsbGFub3guY29tPjsgJ0ZyZWVCU0Qtc3RhYmxlQEZyZWVCU0Qub3JnJyA8RnJlZUJT RC1zdGFibGVARnJlZUJTRC5vcmc+OyBmcmVlYnNkLWFyY2ggPGZyZWVic2QtYXJjaEBmcmVlYnNk Lm9yZz4NClN1YmplY3Q6IFJlOiBbSEVBRFMgVVBdIC0gT0ZFRC9SRE1BIHN0YWNrIHVwZGF0ZQ0K DQpPbiAwMy8xNy8yMDE4IDEzOjAzLCBIYW5zIFBldHRlciBTZWxhc2t5IHdyb3RlOg0KPiBPbiAw My8xNy8xOCAyMDo1MiwgTmF2ZGVlcCBQYXJoYXIgd3JvdGU6DQo+PiBIb2xkIHlvdXIgaG9yc2Vz LsKgIERvIHlvdSBoYXZlIGNvbmZpcm1hdGlvbiBmcm9tIHRoZSBhZmZlY3RlZCBwYXJ0eSANCj4+ IHRoYXQgdGhlIHNoaW1zIGFyZSBhZGVxdWF0ZSBmb3IgdGhlbT/CoCBJIGhhdmUgYmVlbiB3YWl0 aW5nIGZvciB0aGF0IA0KPj4gYmVmb3JlIGxvb2tpbmcgYXQgdGhpcyBicmFuY2guDQo+IA0KPiBI aSBOYXZkZWVwLA0KPiANCj4gTWVsbGFub3ggaGFzIHJlY2VpdmVkIGFuIEFQSSBsaXN0IGZyb20g YXQgbGVhc3Qgb25lIHBhcnR5LCBhbmQgaGFzIA0KPiB0YWtlbiB0aGUgYWN0aW9uIHRvIHN1cHBv cnQgYWxsIHRoZSByZXF1aXJlZCBBUElzLg0KPiANCj4+IElzIHRoZSBpd19jeGdiZSBicmVha2Fn ZSBhIHNpbXBsZSBtZXJnZSBjb25mbGljdCBhcyBwcmV2aW91c2x5IA0KPj4gZGlzY3Vzc2VkIG9y IGRvIHRoZSBzaGltcyByZXF1aXJlIGRyaXZlciBjaGFuZ2VzPw0KPiANCj4gSXQgaXMgYSBtZXJn ZSBjb25mbGljdC4gVGhlIGNvZGUgYWxyZWFkeSBjb21waWxlcyBpbiAxMi1jdXJyZW50Lg0KDQpJ IHRyaWVkIGJhY2tpbmcgb3V0IHIzMjkzOTEgYW5kIHIzMjkwMTcgaW4gYSBsb2NhbCBjb3B5IGFu ZCB0aGVuIHdhcyBhYmxlIHRvIG1lcmdlIHIzMjA0MTgsIHIzMjMwODIsIGFuZCByMzI2MTY5IGlu IHRoYXQgb3JkZXIgd2l0aG91dCBhbnkgY29uZmxpY3RzLiAgQnV0IGl3X2N4Z2JlL2NtLmMgc3Rp bGwgZG9lc24ndCBjb21waWxlIGluIHRoZSBwcm9qZWN0cyBicmFuY2ggYmVjYXVzZSBpdCBoYXMg c29tZSBzb2NrZXQgY29kZSB0aGF0IHJlbGllcyBvbiBzb21lIG9mIGdsZWJpdXMncyBjaGFuZ2Vz IGF2YWlsYWJsZSBvbmx5IGluIGhlYWQgKEkgY2hlY2tlZCB3aXRoIGhpbSBhbmQgdGhleSBhcmVu J3QgTUZDJ2FibGUpLiAgSSdtIHRyeWluZyB0byBmaWd1cmUgb3V0IHdoYXQgdG8gZG8gYWJvdXQg dGhvc2UuDQoNCkFuZCB3aGF0IGFib3V0IHRoZSBjeGdiIGJyZWFrYWdlPyAgSXMgdGhlcmUgYW55 IHNpbXBsZSB3YXkgdG8gbWFrZSBhbiBvbGQgc3R5bGUgZHJpdmVyIHdvcmsgd2l0aCB0aGUgbmV3 IHN0YWNrPyAgVDMgaXdfY3hnYiBpbiBoZWFkIHdhcyByZXRpcmVkIGJlZm9yZSB0aGUgb2ZlZCBv dmVyaGF1bC4NCg0KUmVnYXJkcywNCk5hdmRlZXANCg0K From owner-freebsd-arch@freebsd.org Thu Mar 22 20:37:34 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 3A13AF696EC; Thu, 22 Mar 2018 20:37:34 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 B6E3E6A1D5; Thu, 22 Mar 2018 20:37:33 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id f125so18458009wme.4; Thu, 22 Mar 2018 13:37:33 -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=bTTEGC4bxXV9VWskmJ+XUHvUmFSddzsDWEci5AUklFU=; b=AEaONByuIPmX/AFJjohmxxJ88OAyC3nb9E2Gl2VHT59jwzBKsJg7hdKf4C86gg/Z6P faSC35WVTGg7nVOitFbT/nFngKj77O0zA0dYGz1lvOdodPe+BWOh0pHKOWlkV77p1SPl QSqOA0Xi2jDDZmFk8qA+mFr4S6UxJ8BB08k9eu5DXCMGR4BhLWKdv8gbPAIdRdfwn/aN OwSPgS/PjSyfy4Y+OIyrV1PHKmFYnhP+bGJNxmJ+vcjJGnif0SinZvNSXg29tU2VMYHI tc/DJ8QjrmWbhTExGApRGRpmqEEFz+spIXldcWPegBQUu0Pn3G+KDIcjpJUumItnN225 Qe7w== 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=bTTEGC4bxXV9VWskmJ+XUHvUmFSddzsDWEci5AUklFU=; b=KOMJiHeUrNK0F+8WJ4yaaKOTGnvmTNuDmfyA92aN9eFa0vDUkBlv4W97GZbeCYQ6Tv 6rcbLFH6HLD0tDcY6BaBe1oDhtQc8B3xkyXUymm/ZfLVKxwE+pndgv1funFpxx7l/PWC 7BpVLOdhQ6KjnGyXnoUsJC9aW3FpFbNacAQ18ToM5QNUUAqCZnWDlhiqgR2vGHaVhYrd NblajIn0mwQ7abHi2hynNRPfIp444nT5wn6Qt+ZdSWlmJi+wy7DqdiQPc78pIJO8FP88 PLfEOnNSl6mAE3jeNTyqYa6bTMAiIRYZWsatvYrkzaEDHf0jEUieCKnZEI5bhqyTCOuf +CHA== X-Gm-Message-State: AElRT7EKZ5T6+Ybipw//TzGctw+9tUINm/4Zahcdr1hjVAQHnhY08NwA 6ncj6K8EgNIPd4VCY4WPdXXHvee3 X-Google-Smtp-Source: AG47ELugfQaH6FygNuBWVfMizFCUilu+vsGhAqxO9h6c7jYLOg1d/lebU2HFJTg68sQHDwuP3T0OtA== X-Received: by 10.28.220.2 with SMTP id t2mr7141293wmg.21.1521751052284; Thu, 22 Mar 2018 13:37:32 -0700 (PDT) Received: from [10.192.166.0] (stargate.chelsio.com. [12.32.117.8]) by smtp.googlemail.com with ESMTPSA id v23sm6815589wmc.22.2018.03.22.13.37.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 13:37:31 -0700 (PDT) Sender: Navdeep Parhar Subject: Re: [HEADS UP] - OFED/RDMA stack update To: Meny Yossefi , Hans Petter Selasky , Konstantin Belousov , "'freebsd-infiniband@freebsd.org'" , freebsd-drivers , "'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> <1cbfc0c9-25bc-3373-8ce8-4c5e072cd6fe@FreeBSD.org> From: Navdeep Parhar Message-ID: Date: Thu, 22 Mar 2018 13:37:27 -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: 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: Thu, 22 Mar 2018 20:37:34 -0000 iw_cxgbe still doesn't build in the branch because of some socket changes in head that are not in 11. I need to add the 11 equivalent of the dequeue_socket code to iw_cxgbe to get it to compile, and then try it to see if it actually works. Regards, Navdeep On 03/22/2018 04:36, Meny Yossefi wrote: > Hi Navdeep,=20 >=20 > What's the current iWARP status on the project branch?=20 > If it's ready we'd like to merge it to FreeBSD11-STABLE immediately.=20 >=20 > -Meny >=20 >=20 > -----Original Message----- > From: Navdeep Parhar [mailto:nparhar@gmail.com] On Behalf Of Navdeep Pa= rhar > Sent: Tuesday, March 20, 2018 10:08 PM > To: Hans Petter Selasky ; Konstantin Belousov ; 'freebsd-infiniband@freebsd.org' ; freebsd-drivers ; Meny Yossefi ; 'FreeBSD-stable@FreeBSD.org' ;= freebsd-arch > Subject: Re: [HEADS UP] - OFED/RDMA stack update >=20 > 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 pa= rty=20 >>> that the shims are adequate for them?=C2=A0 I have been waiting for t= hat=20 >>> before looking at this branch. >> >> Hi Navdeep, >> >> Mellanox has received an API list from at least one party, and has=20 >> taken the action to support all the required APIs. >> >>> Is the iw_cxgbe breakage a simple merge conflict as previously=20 >>> discussed or do the shims require driver changes? >> >> It is a merge conflict. The code already compiles in 12-current. >=20 > I tried backing out r329391 and r329017 in a local copy and then was ab= le to merge r320418, r323082, and r326169 in that order without any confl= icts. But iw_cxgbe/cm.c still doesn't compile in the projects branch bec= ause it has some socket code that relies on some of glebius's changes ava= ilable only in head (I checked with him and they aren't MFC'able). I'm t= rying to figure out what to do about those. >=20 > And what about the cxgb breakage? Is there any simple way to make an o= ld style driver work with the new stack? T3 iw_cxgb in head was retired = before the ofed overhaul. >=20 > Regards, > Navdeep >=20 From owner-freebsd-arch@freebsd.org Fri Mar 23 10:38:49 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 1B24DF5DCBE; Fri, 23 Mar 2018 10:38:49 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) (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 9DA876C543; Fri, 23 Mar 2018 10:38:48 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f50.google.com with SMTP id o102-v6so17555142lfg.8; Fri, 23 Mar 2018 03:38:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=RnkJwCPMB8DlCuQU/E3+vvPcKP34ZPwz99FZCPBfc5c=; b=fhZXjHrLMS6SluBMOJu7DGQEm0zjmpPithEAssHBs4f58mDbyVDlP1yuftHL0C4QM4 oqa5hQT3gSs45DXyHzhI+fYrneepWhZ4INxX5QC7qVABUIeDKR4W+73+bxfdkrZmq1h6 au1hfva9iK/0v3qnMrVBZ3M1P6zOLQ6B3cu7uNiF6B2Zot6z4sxAsAa5q/u9dlr325Eu 3UeDlWZxULq+z6LqjZLhdgeAliWinl51pluMjBA9oT/YmTdvlGCVAO1aR9nQVOkMNG6d DRsMb7WpriQi+7hXf/4DdJ6bxLXQ1vvL74S3OsJxuBBbshvMHKiO5ngR0+9Ugzjx5LkI ZhoA== X-Gm-Message-State: AElRT7GNLQIs+fiW5eVxZoEiEx2KLGRqWGqXSeLcTKads72GFC2xjzAO hrLh1kFrQUD5YRewNES5OAzwdJcTbb8= X-Google-Smtp-Source: AG47ELudZztuJ+KMhwsk6ykow8i8drgXxR2h2TslPx9uij9f0syZ2JYJwqaDPyFJjGgcdQI4fMWVaQ== X-Received: by 2002:a19:1754:: with SMTP id n81-v6mr16898162lfi.113.1521801526843; Fri, 23 Mar 2018 03:38:46 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id a9-v6sm2100794lfk.80.2018.03.23.03.38.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Mar 2018 03:38:45 -0700 (PDT) Subject: Re: geom->access problem and workaround To: Poul-Henning Kamp , Warner Losh Cc: "freebsd-arch@freebsd.org" , freebsd-geom@freebsd.org References: <809d9254-ee56-59d8-69a4-08838e985cea@FreeBSD.org> <56619.1520878022@critter.freebsd.dk> From: Andriy Gapon Message-ID: <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> Date: Fri, 23 Mar 2018 12:38:44 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <56619.1520878022@critter.freebsd.dk> Content-Type: text/plain; charset=utf-8 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: Fri, 23 Mar 2018 10:38:49 -0000 On 12/03/2018 20:07, Poul-Henning Kamp wrote: > If we want to have an architectural sound way to do slow operations > before any "user-I/O" is initiated, the right way to do so is to > define new BIO_OPEN and BIO_CLOSE operation, and insist via asserts > than all BIO_{READ|WRITE|DELETE} are wrapped in these. In support of this proposal I want to add another example. The problem is not only with doing I/O in access, but also with doing blocking I/O in the normal I/O path. The following happened when a userland program tried to read from a CD-ROM while its tray was open: panic: sleepq_add: td 0xfffff80008e1c000 to sleep on wchan 0xfffff801e58b8048 with sleeping prohibited cpuid = 0 curthread: 0xfffff80008e1c000 time = 1521652565 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff804670bb = db_trace_self_wrapper+0x2b/frame 0xfffffe07e1886750 kdb_backtrace() at 0xffffffff806d4c79 = kdb_backtrace+0x39/frame 0xfffffe07e1886800 vpanic() at 0xffffffff80699da6 = vpanic+0x166/frame 0xfffffe07e1886840 kassert_panic() at 0xffffffff80699adb = kassert_panic+0x16b/frame 0xfffffe07e18868b0 sleepq_add() at 0xffffffff806e1902 = sleepq_add+0x342/frame 0xfffffe07e1886910 _sleep() at 0xffffffff806a41f7 = _sleep+0x2b7/frame 0xfffffe07e18869b0 cam_periph_ccbwait() at 0xffffffff802b53ad = cam_periph_ccbwait+0x5d/frame 0xfffffe07e18869e0 cam_periph_runccb() at 0xffffffff802b51d8 = cam_periph_runccb+0xb8/frame 0xfffffe07e1886a40 cdrunccb() at 0xffffffff802d52fc = cdrunccb+0x3c/frame 0xfffffe07e1886a60 cdprevent() at 0xffffffff802d4beb = cdprevent+0x7b/frame 0xfffffe07e1886aa0 cdcheckmedia() at 0xffffffff802d48b2 = cdcheckmedia+0x22/frame 0xfffffe07e1886af0 cdstrategy() at 0xffffffff802d2a36 = cdstrategy+0x56/frame 0xfffffe07e1886b20 g_disk_start() at 0xffffffff80608330 = g_disk_start+0x170/frame 0xfffffe07e1886b70 g_io_schedule_down() at 0xffffffff8060c1db = g_io_schedule_down+0x1eb/frame 0xfffffe07e1886b90 g_down_procbody() at 0xffffffff8060cbdd = g_down_procbody+0x6d/frame 0xfffffe07e1886ba0 fork_exit() at 0xffffffff8065e410 = fork_exit+0xd0/frame 0xfffffe07e1886bf0 fork_trampoline() at 0xffffffff808e4aee = fork_trampoline+0xe/frame 0xfffffe07e1886bf0 But maybe I am overgeneralizing. Maybe it's just silly that cdstrategy tries perform media manipulations instead of just failing a request. Apparently the device was already opened, but the prevent-allow bit was changed by something else (e.g. via the pass device) and that allowed to get the tray opened. What do you think? -- Andriy Gapon From owner-freebsd-arch@freebsd.org Fri Mar 23 10:47:42 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 5BE93F5E928; Fri, 23 Mar 2018 10:47:42 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id EEF9B6CDD9; Fri, 23 Mar 2018 10:47:41 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id C993C273B0; Fri, 23 Mar 2018 10:47:34 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w2N9U4NX000890 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 23 Mar 2018 09:30:04 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w2N9U3gJ000889; Fri, 23 Mar 2018 09:30:03 GMT (envelope-from phk) To: Andriy Gapon cc: Warner Losh , "freebsd-arch@freebsd.org" , freebsd-geom@freebsd.org Subject: Re: geom->access problem and workaround In-reply-to: <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> From: "Poul-Henning Kamp" References: <809d9254-ee56-59d8-69a4-08838e985cea@FreeBSD.org> <56619.1520878022@critter.freebsd.dk> <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <887.1521797403.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Fri, 23 Mar 2018 09:30:03 +0000 Message-ID: <888.1521797403@critter.freebsd.dk> 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: Fri, 23 Mar 2018 10:47:42 -0000 -------- In message <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org>, Andriy Gapo= n writes: >On 12/03/2018 20:07, Poul-Henning Kamp wrote: >> If we want to have an architectural sound way to do slow operations >> before any "user-I/O" is initiated, the right way to do so is to >> define new BIO_OPEN and BIO_CLOSE operation, and insist via asserts >> than all BIO_{READ|WRITE|DELETE} are wrapped in these. >What do you think? I don't see that changing anything... GEOM rests on a set of assumptions, if you violate them, you get panics. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-arch@freebsd.org Fri Mar 23 13:26:22 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 F38B9F6C2B8 for ; Fri, 23 Mar 2018 13:26:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 87F4D73CFA for ; Fri, 23 Mar 2018 13:26:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x233.google.com with SMTP id q80so4237695ioi.13 for ; Fri, 23 Mar 2018 06:26:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ugh28Ml5qpKKmSDdaCpdU+52DDJneW1msRSYr9yW60Y=; b=USaYwdcmbdBUAjTgZ1T1k2A3ewI99nFLKk2iELNp4+WtP6lKqm5+eSCwFoHJRiqH7r jgjH64GrO8dvT4/X4mIVZtg4DaWRD969ONAGO23mMUr6AKw4Fo1vNfqIqeSdnVCzH9N0 IEUNsce6KWqlIFQmywG1eGCKSxHiqpLxc6wd42iTTOHG6O48BT++KhfjQoudfsztQBcp rqBIV+MLBL48oAxVXXsYB/P8q5rCRC07ay6ilBBO5/sQeUms2W8mJZk+uMajJ6uMQTQB OXZHIzLdV5lySPiFDOiyUt1SKoOa7XEdOcqlNLzus17etj4luHKPxwC4z0Nj4bPW5+ZF a3SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ugh28Ml5qpKKmSDdaCpdU+52DDJneW1msRSYr9yW60Y=; b=oH9Le8OnaROrmSmhRKMKY/vrhwCQ1saP5MCqxqmAS2XqUfJlHx71rATAORlqF9VBFO LvPij7ptFD6ziFp7/CB0xUKmzVpfaJzeHjOhMXKn2qfZ7mTAEOEI6wEXzM1DbTcpK8JK YeLPJ1odPRb6U9prXP0rIvpMjXH0xE3aDGsyQs0MFAJ7LNRgWfuPV0XUb3Ankln1/ZAA xGpODxmfFNiXDERIF+dUqmIZcr9obrLbeNT0HCqdu7PrrzJKbjtFUB68ngFuasbe11G9 fv/GymBezU2bseSSyKD0fP0RuWvv/3KQKUkLBPSDhbV54v4rmlyBm8TpcIXvTVE75JhN eqOg== X-Gm-Message-State: AElRT7FcHYxCphMwUjWfhHkFTGRc4+d1BU7ERRv//d73VrN/nQ9JHxkm J5daxLm+b8DReSGfaMWJ/jjeBfkWCmb/fCQpLAM3CA== X-Google-Smtp-Source: AG47ELtCk3iCOOuDXu2mLkifesZ0MzlzShtKwTfvrFXjdQRN8Ff7fmBO7ND//xvJf+6Gt3MewFBIbz/UFgp6KJr/6kM= X-Received: by 10.107.144.11 with SMTP id s11mr30319147iod.37.1521811580519; Fri, 23 Mar 2018 06:26:20 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Fri, 23 Mar 2018 06:26:19 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:18a2:a4f7:170:8dd9] In-Reply-To: <888.1521797403@critter.freebsd.dk> References: <809d9254-ee56-59d8-69a4-08838e985cea@FreeBSD.org> <56619.1520878022@critter.freebsd.dk> <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> <888.1521797403@critter.freebsd.dk> From: Warner Losh Date: Fri, 23 Mar 2018 07:26:19 -0600 X-Google-Sender-Auth: RTDvmECwPqKjp3mie1_rAEW99j8 Message-ID: Subject: Re: geom->access problem and workaround To: Poul-Henning Kamp Cc: Andriy Gapon , "freebsd-arch@freebsd.org" , freebsd-geom@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 23 Mar 2018 13:26:22 -0000 On Fri, Mar 23, 2018 at 3:30 AM, Poul-Henning Kamp wrote: > -------- > In message <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org>, Andriy > Gapon writes: > >On 12/03/2018 20:07, Poul-Henning Kamp wrote: > >> If we want to have an architectural sound way to do slow operations > >> before any "user-I/O" is initiated, the right way to do so is to > >> define new BIO_OPEN and BIO_CLOSE operation, and insist via asserts > >> than all BIO_{READ|WRITE|DELETE} are wrapped in these. > > >What do you think? > > I don't see that changing anything... > > GEOM rests on a set of assumptions, if you violate them, you get panics. I agree. The cd panic is a problem in the cd driver where it bogusly uses runccb in a context that can't sleep. Warner From owner-freebsd-arch@freebsd.org Fri Mar 23 13:31:16 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 A8B24F6C882 for ; Fri, 23 Mar 2018 13:31:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 248347407E for ; Fri, 23 Mar 2018 13:31:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id 141so15150578iou.12 for ; Fri, 23 Mar 2018 06:31:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AoVRnoozLtO9SyxnFjtFKt13Uy2kljmz15rSsGuHkb0=; b=JUYg5+AjbNM+JV/xPuewpGnEofVeWRqGHOiZYyXJ5Im/D6lbeol3IZXBvv2XEJVDnh ERXGwmNBSORK4Tn32MgZw6nWU+JuugIqHrB/KtzZ0CccnrSNbFe9lVWE4bQlSKs7CzC/ KWMsodcPxxJ5SxHF/y03QuTvaHuwF8jAjWZVM/8EDhEjmRxF/MTfJ0Rr+UzmM99sC1oq yAF9NwRTa20ZdyPgV8V5zKJEhLkSe3p0UsAjD7daeFcvm81m8kEDvOev+V/A3RL06WhI Zb1vkEL2AVjrNW8Fdf+1Jjpy25DGvHajP48UOhGmXpgQ7wTZXtkQxvFEoPS0N3x27S/K YwRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AoVRnoozLtO9SyxnFjtFKt13Uy2kljmz15rSsGuHkb0=; b=QLctfXqoCwe6oSqjf8w0XGpmclhMtgnbZiM2LV6IN9wFduLmtTf4pfaGF6dfV0gyaU pyv4nACalKxsA+chwo6Q11ubQkb8h9HrXU9cFryso6QyXb+D3/viInikFh2YzKN5rb2d 3hvsBjCryZXB2T9xlNYB4IlRDgrMqJgrk0pcxZdxX8KAVoch/ZN7PL6rEUHgvLX8NrV+ Srid4rUt7NM5cgZhH0qdvicuM2GzdwRWRVoCQf5AO684YuKIhgvbuLfAeOwmKBUnLJLZ RNLQ0GIJ/GUyl5ECk4OX4cq5HI6phUQ9GiQiX/BzZvZqheCepM8S5RJ1vRyefZCXfDlf 6SCw== X-Gm-Message-State: AElRT7Eg1wiwu5OUsZShSoo2a+PPpFWijSie7UAF1VVKuhOKaHDFGFtC 9jYS6P4R9cSW7591F4oKGAhRd1+0o5+l9AxSM4V4Xg== X-Google-Smtp-Source: AG47ELtXbkgrg7zfkIR7FsHvb9H9FB9VjaN8Xz4UXcIoJ5IrzzbJ663ui6agaZnp03sVFaZjug+dqFm7/rl58o8nWHQ= X-Received: by 10.107.58.134 with SMTP id h128mr29447583ioa.299.1521811875502; Fri, 23 Mar 2018 06:31:15 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Fri, 23 Mar 2018 06:31:14 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:18a2:a4f7:170:8dd9] In-Reply-To: <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> References: <809d9254-ee56-59d8-69a4-08838e985cea@FreeBSD.org> <56619.1520878022@critter.freebsd.dk> <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> From: Warner Losh Date: Fri, 23 Mar 2018 07:31:14 -0600 X-Google-Sender-Auth: kpEyGCL0IYYV3dHyl3t97cIGIjk Message-ID: Subject: Re: geom->access problem and workaround To: Andriy Gapon Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" , freebsd-geom@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 23 Mar 2018 13:31:17 -0000 On Fri, Mar 23, 2018 at 4:38 AM, Andriy Gapon wrote: > On 12/03/2018 20:07, Poul-Henning Kamp wrote: > > If we want to have an architectural sound way to do slow operations > > before any "user-I/O" is initiated, the right way to do so is to > > define new BIO_OPEN and BIO_CLOSE operation, and insist via asserts > > than all BIO_{READ|WRITE|DELETE} are wrapped in these. > > > In support of this proposal I want to add another example. > The problem is not only with doing I/O in access, but also with doing > blocking > I/O in the normal I/O path. > The following happened when a userland program tried to read from a CD-ROM > while > its tray was open: > > panic: sleepq_add: td 0xfffff80008e1c000 to sleep on wchan > 0xfffff801e58b8048 > with sleeping prohibited > cdstrategy shouldn't be sleeping. It can start I/O, but it can't wait for it to finish. strategy has been a no-sleep-zone since at least v6. The fact it's waiting for prevent is the bug here. Waner From owner-freebsd-arch@freebsd.org Fri Mar 23 19:19:08 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 9CD97F664D0 for ; Fri, 23 Mar 2018 19:19:08 +0000 (UTC) (envelope-from mcgrof@kernel.org) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (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 427EA8760F; Fri, 23 Mar 2018 19:19:07 +0000 (UTC) (envelope-from mcgrof@kernel.org) Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 99E3321835; Fri, 23 Mar 2018 19:19:06 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 99E3321835 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=mcgrof@kernel.org Received: by mail-it0-f46.google.com with SMTP id y20-v6so3878076itc.5; Fri, 23 Mar 2018 12:19:06 -0700 (PDT) X-Gm-Message-State: AElRT7FsoD8BlWD99TDoCYZaY7TJzFevpYovJbEz5cngs6gKWm5a77kY COB9SM/BZ8Ipm4CorZaOs7cAoWRLN70VSFF/Ghk= X-Google-Smtp-Source: AG47ELsTKAczVwnZgEDeZDB6TQCAosw2y/Aq2uUDiwCdhbM6m01CQDSnVswNFF2tjorKROI5hzlzNV7mdhXT/ByBom0= X-Received: by 2002:a24:6f04:: with SMTP id x4-v6mr14800910itb.51.1521832746093; Fri, 23 Mar 2018 12:19:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.128.161 with HTTP; Fri, 23 Mar 2018 12:18:45 -0700 (PDT) From: "Luis R. Rodriguez" Date: Fri, 23 Mar 2018 12:18:45 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: FreeBSD and xfsprogs ? To: freebsd-arch@freebsd.org Cc: Carlos Maiolino , "Darrick J. Wong" , Adrian Chadd Content-Type: text/plain; charset="UTF-8" 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: Fri, 23 Mar 2018 19:19:08 -0000 On the Linux xfs development list there is an RFC to remove IRIX, Darwin, and FreeBSD support from xfsprogs, the userspace program used to create/interact with XFS filesystems. Just wanted to poke and check to ensure that FreeBSD is not interested in XFS, if this is incorrect now would be the good time to chime into the list and discussion. [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys.redhat.com Luis From owner-freebsd-arch@freebsd.org Fri Mar 23 19:51:11 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 2EC8CF691ED for ; Fri, 23 Mar 2018 19:51:11 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) (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 BCB6889165 for ; Fri, 23 Mar 2018 19:51:10 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f50.google.com with SMTP id v194-v6so4007848itb.0 for ; Fri, 23 Mar 2018 12:51:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=TIA/UY2Z088fp0a+EsjbQAUHDf9RblzmYB94KZUDvUE=; b=S6hZ1CeMRn7dRBcsT4PaF100uOPMFP5mcLQg2BlrDaOYEfsrd0V6NlCvThhSapw9no bZN1WKkWblsI3KykHKi7d6PmEo7LzbGtDIG8kif15ZBOsBR1+IxVQD4YRUKj7Gest4L7 XrmVj/xnjwG5n+ErPhccN0/rTtIOSnnNGORHzRv94ivPXL2fS5hEV+FYKhBWPdC3kiyV w+VjKrmdb1gDa2w6nGHhBupDDasCDqrOkssrUuv+iAvbLWbu5dNlv4uOMxegtDu9Ah5b Ge/vdyl/RgQmLK68kJN4XwZcUYrdBn2mf26540OBQKYufBmyWWw/xnzV+SuvfqXATia9 f3UQ== X-Gm-Message-State: AElRT7F0Wos8p6UpjEyzqu+c3MwQfTRkNfS4lpho6dGtWSDJph+okuVr /AAfqVWSdi57caMhjZ1xiT/NtlUm X-Google-Smtp-Source: AIpwx4/JQTs8RsbB6ZJfN/UJrxCTO0wLJZ574g5/GJ1kVdNmp7lhwPtSciL1SZT/pq+mypg4LirN8g== X-Received: by 2002:a24:5c90:: with SMTP id q138-v6mr5842903itb.57.1521833288376; Fri, 23 Mar 2018 12:28:08 -0700 (PDT) Received: from mail-it0-f49.google.com (mail-it0-f49.google.com. [209.85.214.49]) by smtp.gmail.com with ESMTPSA id x87-v6sm5027037ita.35.2018.03.23.12.28.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Mar 2018 12:28:08 -0700 (PDT) Received: by mail-it0-f49.google.com with SMTP id k135-v6so3872472ite.2 for ; Fri, 23 Mar 2018 12:28:08 -0700 (PDT) X-Received: by 2002:a24:e14e:: with SMTP id n75-v6mr13613136ith.58.1521833288067; Fri, 23 Mar 2018 12:28:08 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.62.19 with HTTP; Fri, 23 Mar 2018 12:28:07 -0700 (PDT) In-Reply-To: References: From: Conrad Meyer Date: Fri, 23 Mar 2018 12:28:07 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: FreeBSD and xfsprogs ? To: "Luis R. Rodriguez" Cc: "freebsd-arch@freebsd.org" , Carlos Maiolino , "Darrick J. Wong" Content-Type: text/plain; charset="UTF-8" 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: Fri, 23 Mar 2018 19:51:11 -0000 On Fri, Mar 23, 2018 at 12:18 PM, Luis R. Rodriguez wrote: > On the Linux xfs development list there is an RFC to remove IRIX, > Darwin, and FreeBSD support from xfsprogs, the userspace program used > to create/interact with XFS filesystems. Just wanted to poke and check > to ensure that FreeBSD is not interested in XFS, if this is incorrect > now would be the good time to chime into the list and discussion. > > [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys.redhat.com Hi Luis, FreeBSD 11+ can mount XFS filesystems read and write via a FUSE port incorporating LKL[0] (sysutils/fusefs-lkl). I would appreciate xfsprogs retaining FreeBSD support at least for creating or modifying offline XFS filesystems, if it isn't too painful for you. Thanks, Conrad [0]: https://github.com/lkl/linux From owner-freebsd-arch@freebsd.org Sat Mar 24 02:38:08 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 BEF77F62CF6 for ; Sat, 24 Mar 2018 02:38:08 +0000 (UTC) (envelope-from vdasahar@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 50D2672933 for ; Sat, 24 Mar 2018 02:38:08 +0000 (UTC) (envelope-from vdasahar@gmail.com) Received: by mail-io0-x229.google.com with SMTP id b20so17302459iof.5 for ; Fri, 23 Mar 2018 19:38:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=AgqG8THBzfAl6uR/YsSBRXDHi/bdA2qzCqdPWHbgTYU=; b=TEzxUsAjDzQDIfmIQlMiBaWEg/iMPcZuWtScIkRTVxhmGp4G/PSVBd0sEPU0IZe4L1 3IjfjQ6rh0VCtp2hQSgkRPpe7e3+n0D0cKHZli9TYomr4DNHHvmnvgBheYAnneOFBhCY /seyx+T3XMEN9EP2kfZzP6caV95oVSAJR+vq9OSNLYHVxtfoId91MqjK6vSzeuRtOT79 4aWMdg2rgm8ZxTMXzheJY29uuZZbY/y62CqmWIueAA3fJkByNSha3dsv4G9/1gWqln9V 5L+cDgTuEoSBQInUtOOtRCPPN4emZt0cdQjgdaxFtVRj458j8Qc6Pi64ChiwGmwSW9W6 mEmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=AgqG8THBzfAl6uR/YsSBRXDHi/bdA2qzCqdPWHbgTYU=; b=RpIh4do6CLvW1oo+Lq0P1wnhc2p9LnM/MaamFQUl4kbqyIXnqsmvg07h/0pIuCLwVh QXW0NWjCv6ZA6mYTy6JRLoJfJcfkgwLWltdxNE7HywG0z5XJtw0SDDWEE4Gbqun/R8wN p84fNi7JxdkMk+Ubx7VsXdkW6TxCnsxxZdqTqBbVeOyjBhAIE2XI1yDteG0q97bwYDcR 5fnzSB85ZiraI3QeUqAydskVCvgIFQUTals4BeMgxa1JzJTnMqFT+dQxuxsTfLfsoGlh 9pvoZuKGkuTbeorbl8cK/5MjRTYHbsB4v4gehfNJsEy5gp3vGBEx3QeEFZwpAnd+rGKk JqIA== X-Gm-Message-State: AElRT7FtMtT7tc18hmtq5EZDfxg5begIkzqLFLeBCAWiUZWAziea9uTm mUclC0S2WGkNrP+V1+U9xjDBtkLIaI6OSeo1tO58Kg== X-Google-Smtp-Source: AG47ELssbsHqn6VeAzG+qk4bLKJzBvuifEC8+ql+bMveMRJOlKxm5ajGcdqgg2hIs+AWGQnZntJM2uM8RuH/3ezqghs= X-Received: by 10.107.36.16 with SMTP id k16mr33038861iok.266.1521859087480; Fri, 23 Mar 2018 19:38:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.176.75 with HTTP; Fri, 23 Mar 2018 19:38:07 -0700 (PDT) From: Vishnu Dasa Date: Fri, 23 Mar 2018 19:38:07 -0700 Message-ID: Subject: Pointers for adding a new sockets protocol To: freebsd-arch@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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, 24 Mar 2018 02:38:08 -0000 Hello Everyone, I'm looking for some pointers on how to add a new sockets protocol in FreeBSD. Something on the lines of https://linuxwarrior.wordpress.com/2008/12/02/add-a-new-protocol-to-linux-kernel/ would be greatly helpful. If you can redirect me to other mailing lists, that would be helpful too. Thanks in advance! Regards, Vishnu