From owner-freebsd-infiniband@FreeBSD.ORG Fri May 29 11:05:47 2015 Return-Path: Delivered-To: freebsd-infiniband@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4452EC31 for ; Fri, 29 May 2015 11:05:47 +0000 (UTC) (envelope-from vadim@alimov.net) Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) (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 C63B01B6D for ; Fri, 29 May 2015 11:05:45 +0000 (UTC) (envelope-from vadim@alimov.net) Received: by laat2 with SMTP id t2so52952924laa.1 for ; Fri, 29 May 2015 04:05:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=nyAx+p5iOj7/83ehdiaJ7kITg3NFR4w9M40KnL+JHJE=; b=ffB9/+2Uz2eXyiS+w6+3StCCEfBEIGVxkk6pPJ9zSoFjAgIo1IXxh5u7pqaz0Q0B9e qPSboecGnnNlWV8gWCRNs+3lu3YWOyGJHaGngJQzPmmFEqKTzfNo5kM+hR5wCv+Pvz+j 0bHoD+lBKdrgvTIgZ4jHKsoZI3yCQEP7AH3duxGlkdXRdxNTBTbp7U6qIq9tJKgPIZSr H5MH0Kru1uyEW+q+wE5DsFSoaO1f0jdp0lfZ1HhCDa5rDCglVUY2rVGU3CFVbc6FZo9q cfMboFvqauKpRMApI1LqBS6fnQKDNboXv011JlmKhx4MBBE5jK4UwK4JOQ2byKYfPFYZ ziGA== X-Gm-Message-State: ALoCoQmdkou7bzQrDuVzzkjjWVYfRBtg2DG3N3DlqB1S90JQY3LboWCOEKSvQwlIQQSlRy9Z94pM X-Received: by 10.152.1.4 with SMTP id 4mr7415208lai.25.1432897537644; Fri, 29 May 2015 04:05:37 -0700 (PDT) Received: from [172.16.123.101] ([178.158.250.88]) by mx.google.com with ESMTPSA id df8sm1321541lac.3.2015.05.29.04.05.36 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 May 2015 04:05:36 -0700 (PDT) Message-ID: <556847FF.8000004@alimov.net> Date: Fri, 29 May 2015 14:05:35 +0300 From: Vadim Alimov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-infiniband@freebsd.org Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-infiniband@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Infiniband on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2015 11:05:47 -0000 Hi. Did you manage to bring up a mellanox NIC with qsfp port as an ethernet device? I'm facing exactly the same issue. mlx4_core0: mem 0xfbd00000-0xfbdfffff,0xf9800000-0xf9ffffff irq 16 at device 0.0 on pci4 mlx4_core: Mellanox ConnectX core driver v2.1 (May 28 2015) mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.1 (May 28 2015) mlxen0: Ethernet address: 00:21:cc:49:48:93 mlx4_en: mlx4_core0: Port 1: Using 8 TX rings mlx4_en: mlx4_core0: Port 1: Using 8 RX rings Forward thanks for help. Vadim. -- Vadim Alimov CIO Maximum-Net LLC vadim@alimov.net skype: vadim.alimov office: +38 044-374-04-51 ext. 601 cellular: +38 067-827-05-77 From owner-freebsd-infiniband@FreeBSD.ORG Fri May 29 14:32:18 2015 Return-Path: Delivered-To: freebsd-infiniband@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73FAFD62 for ; Fri, 29 May 2015 14:32:18 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A30B1F85 for ; Fri, 29 May 2015 14:32:18 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-07v.sys.comcast.net with comcast id ZqXv1q0042Qkjl901qYFAJ; Fri, 29 May 2015 14:32:15 +0000 Received: from resmail-ch2-217v.sys.comcast.net ([162.150.48.251]) by resomta-ch2-15v.sys.comcast.net with comcast id ZqYF1q00D5RAVJS01qYFEq; Fri, 29 May 2015 14:32:15 +0000 Date: Fri, 29 May 2015 14:32:14 +0000 (UTC) From: rondzierwa@comcast.net To: Vadim Alimov Cc: freebsd-infiniband@freebsd.org Message-ID: <1801993404.23038823.1432909934595.JavaMail.zimbra@comcast.net> In-Reply-To: <556847FF.8000004@alimov.net> References: <556847FF.8000004@alimov.net> Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 MIME-Version: 1.0 X-Originating-IP: [::ffff:50.241.136.195] X-Mailer: Zimbra 8.0.7_GA_6031 (ZimbraWebClient - FF13 (Win)/8.0.7_GA_6031) Thread-Topic: Does mlxen work on FreeBSD 10.1 with ConnectX-3 Thread-Index: UPk/aI2GD0qdGpbAte8qKpPr/I2iMg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1432909935; bh=uWWAdmUAZAto19Y+O6pWJu9pGoFNIHl73N8K34Jk8U4=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=ke8OqrKuN+0texc3QJRJ1Bxg0C8OpGKjEzbdEw7NLciq0nhNSaUNFSOcggZt/Ig31 234acawphvzo4ChoisrSfAW8dh7yzQXSU/jVpyY6/F3v7dhOmkWF+iMaseTrjFCm1/ r7kcuoDHzxjgPwX8AbYqrDN8A0LhbeEf1ABZn6CKQh4cIaLPyk40iAQDJA7jR3j5vh hOR00m6PkDrlolbCNVrBPc1Qtv44CFkPZ6mNzPT77B2d9LlR9YkEW60DAOMn3AXrtu /ENgkYXbPLN9Bb+h+/aqwziid/kLM5QSImmTfzVp5h76zzzQ7XbmVK99L0z3il4Nhl MgpZlyaAYS6Ag== Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-infiniband@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Infiniband on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2015 14:32:18 -0000 You seem to have gotten further than I did, I could not get a driver to recognize the card I was trying to use. Our current approach has been to switch to Solaris. Our options are more plentiful there, and coverage for various hardware seems more complete. >From your dmesg output, it looks like the ethernet device should be there. Try "ifconfig -a". You should see a new device called mlxen0: My plan was to hard configure the IB links in the rc.conf file like: ifconfig_mlxen0="inet 192.168.22.1 netmask 255.255.255.0" ron. ----- Original Message ----- From: "Vadim Alimov" To: freebsd-infiniband@freebsd.org Sent: Friday, May 29, 2015 7:05:35 AM Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 Hi. Did you manage to bring up a mellanox NIC with qsfp port as an ethernet device? I'm facing exactly the same issue. mlx4_core0: mem 0xfbd00000-0xfbdfffff,0xf9800000-0xf9ffffff irq 16 at device 0.0 on pci4 mlx4_core: Mellanox ConnectX core driver v2.1 (May 28 2015) mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.1 (May 28 2015) mlxen0: Ethernet address: 00:21:cc:49:48:93 mlx4_en: mlx4_core0: Port 1: Using 8 TX rings mlx4_en: mlx4_core0: Port 1: Using 8 RX rings Forward thanks for help. Vadim. -- Vadim Alimov CIO Maximum-Net LLC vadim@alimov.net skype: vadim.alimov office: +38 044-374-04-51 ext. 601 cellular: +38 067-827-05-77 _______________________________________________ freebsd-infiniband@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-infiniband To unsubscribe, send any mail to "freebsd-infiniband-unsubscribe@freebsd.org" From owner-freebsd-infiniband@FreeBSD.ORG Fri May 29 16:17:08 2015 Return-Path: Delivered-To: freebsd-infiniband@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A85A82D for ; Fri, 29 May 2015 16:17:08 +0000 (UTC) (envelope-from vadim@alimov.net) Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) (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 92FD2184D for ; Fri, 29 May 2015 16:17:06 +0000 (UTC) (envelope-from vadim@alimov.net) Received: by wgme6 with SMTP id e6so66889749wgm.2 for ; Fri, 29 May 2015 09:16:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=CMChvHcigwAh/TM4aY6GKDBEDEFFN2D5EghzwXrvFds=; b=jda6iN+Ge1D5JGSmJsOnxT2i4f+8jBC6aqjzv40+4t95xGKlDji9G1b4GbQV999h/7 fWhyp+WWVKgTlUZjZBKTWqBwmkRxTYp8x85NupUjNJ+K1I6uSxYouL0or6AVQFDLq8pu TX4dkm3yqwKdWTN+MdvhdSbkFEJ7k6QrG/931O5NSvcvFB3Asw03eUz7QV+K2+ZzMXxd ACel5JSSZgF5M0vKrkdrCISLZ4RzbFoPYHPoVtAC+eyyBoPxPejSqqwLoeWdjaJlOp4t bwnpM+O31Lqq4Sbp3oysAPBi+fv6VJs6PFW42gX3CA9v+FkTGVbL95iDdVh35sLxqgWh waQw== X-Gm-Message-State: ALoCoQlCQqC9N4s70uGZsQU13cu5jQ87HxQfLKEVy7V67EJOXMjmUx5lYR2h+j/82tA+h3SR/mWj X-Received: by 10.194.142.146 with SMTP id rw18mr16051209wjb.110.1432916218912; Fri, 29 May 2015 09:16:58 -0700 (PDT) Received: from [91.234.34.4] ([91.234.34.4]) by mx.google.com with ESMTPSA id m2sm3791288wiy.7.2015.05.29.09.16.57 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 May 2015 09:16:57 -0700 (PDT) Message-ID: <556890F9.6040208@alimov.net> Date: Fri, 29 May 2015 19:16:57 +0300 From: Vadim Alimov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: rondzierwa@comcast.net CC: freebsd-infiniband@freebsd.org Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 References: <556847FF.8000004@alimov.net> <1801993404.23038823.1432909934595.JavaMail.zimbra@comcast.net> In-Reply-To: <1801993404.23038823.1432909934595.JavaMail.zimbra@comcast.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-infiniband@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Infiniband on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2015 16:17:08 -0000 Yeah, there are mlxen0 and mlxen1 devices, but they are "no carrier" whatever i do. As I guess, there are two possible reasons: 1) the qsfp cable i use is incompatible (has a wrong firmware) with mellanox chip 2) freebsd driver does not work I'll try to setup linux. If it goes the same i'll have to order native mellanox cable. I'll write you down the results. Thanks. Regards, Vadim. Vadim Alimov CIO Maximum-Net LLC vadim@alimov.net skype: vadim.alimov office: +38 044-374-04-51 ext. 601 cellular: +38 067-827-05-77 On 05/29/2015 05:32 PM, rondzierwa@comcast.net wrote: > > You seem to have gotten further than I did, I could not get a driver > to recognize the card I was trying to use. > > Our current approach has been to switch to Solaris. Our options are > more plentiful there, and coverage for various hardware seems more > complete. > > From your dmesg output, it looks like the ethernet device should be > there. Try "ifconfig -a". You should see a new device called > mlxen0: My plan was to hard configure the IB links in the rc.conf > file like: > > ifconfig_mlxen0="inet 192.168.22.1 netmask 255.255.255.0" > > > > > ron. > > > > > ------------------------------------------------------------------------ > *From: *"Vadim Alimov" > *To: *freebsd-infiniband@freebsd.org > *Sent: *Friday, May 29, 2015 7:05:35 AM > *Subject: *Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 > > Hi. > > Did you manage to bring up a mellanox NIC with qsfp port as an ethernet > device? > I'm facing exactly the same issue. > > mlx4_core0: mem 0xfbd00000-0xfbdfffff,0xf9800000-0xf9ffffff > irq 16 at device 0.0 on pci4 > mlx4_core: Mellanox ConnectX core driver v2.1 (May 28 2015) > mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.1 (May 28 2015) > mlxen0: Ethernet address: 00:21:cc:49:48:93 > mlx4_en: mlx4_core0: Port 1: Using 8 TX rings > mlx4_en: mlx4_core0: Port 1: Using 8 RX rings > > Forward thanks for help. > Vadim. > > -- > Vadim Alimov > CIO > Maximum-Net LLC > vadim@alimov.net > skype: vadim.alimov > office: +38 044-374-04-51 ext. 601 > cellular: +38 067-827-05-77 > > _______________________________________________ > freebsd-infiniband@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-infiniband > To unsubscribe, send any mail to > "freebsd-infiniband-unsubscribe@freebsd.org" > From owner-freebsd-infiniband@FreeBSD.ORG Fri May 29 16:47:47 2015 Return-Path: Delivered-To: freebsd-infiniband@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD3B1FD9 for ; Fri, 29 May 2015 16:47:47 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A2D80102D for ; Fri, 29 May 2015 16:47:47 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-07v.sys.comcast.net with comcast id Zsnj1q0062GyhjZ01snl8v; Fri, 29 May 2015 16:47:45 +0000 Received: from resmail-ch2-217v.sys.comcast.net ([162.150.48.251]) by resomta-ch2-09v.sys.comcast.net with comcast id Zsnl1q00A5RAVJS01snlL2; Fri, 29 May 2015 16:47:45 +0000 Date: Fri, 29 May 2015 16:47:45 +0000 (UTC) From: rondzierwa@comcast.net To: Vadim Alimov Cc: freebsd-infiniband@freebsd.org Message-ID: <27141688.23164574.1432918065254.JavaMail.zimbra@comcast.net> In-Reply-To: <556890F9.6040208@alimov.net> References: <556847FF.8000004@alimov.net> <1801993404.23038823.1432909934595.JavaMail.zimbra@comcast.net> <556890F9.6040208@alimov.net> Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 MIME-Version: 1.0 X-Originating-IP: [::ffff:50.241.136.195] X-Mailer: Zimbra 8.0.7_GA_6031 (ZimbraWebClient - FF28 (Win)/8.0.7_GA_6031) Thread-Topic: Does mlxen work on FreeBSD 10.1 with ConnectX-3 Thread-Index: ndTMsW++G9sy7nET2ph2PAnc285lwQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1432918065; bh=ByeWZmaxmmYkIpYOwk6OlzzZDELQOcE9VcBuh8xEeWo=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=JlntPFFBv9HR2VDKRZm4JWh/s512omQm2ZaWrrYN4UChZVhbH3tpX4aweMlVd0sRo i9dj8u1c1Z5pWm6q81+vNBxBvTOGLJ4CmcheH8TrIWpHfeKZgtkf0zuUbUZvAtnLmP MeP4X65AouXziyHhLSkuwuQ3PMUhWAmCNuYtuVLe4tgH0fG/Mq1CdeTdI0miSkc4jZ OrRd6JAho95vSAn6ktFViw+D/ZVlQYhDqK3LeKDR6FJzFraZhwmsrcJ62jB670k8Ow VXfDpuNEzVAks5WypYLm78DgEODQWJkeOTZlEZiEGE5Jyud21HlRKlnAFegXdCAfo3 4SERNgmxBJqkw== Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-infiniband@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Infiniband on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2015 16:47:48 -0000 Sounds like either the cable is wrong, or the other end that its connected to isn't active. Try connecting both ports together. If the cable is right, they both should see carrier. Once the cable is connected, you might have to do an ifconfig on each one to turn it on. something like ifconfig mlxen0 192.168.20.1 netmask 255.255.255.0 up ifconfig mlxen1 92.168.20.2 netmask 255.255.255.0 up ron. ----- Original Message ----- From: "Vadim Alimov" To: rondzierwa@comcast.net Cc: freebsd-infiniband@freebsd.org Sent: Friday, May 29, 2015 12:16:57 PM Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 Yeah, there are mlxen0 and mlxen1 devices, but they are "no carrier" whatever i do. As I guess, there are two possible reasons: 1) the qsfp cable i use is incompatible (has a wrong firmware) with mellanox chip 2) freebsd driver does not work I'll try to setup linux. If it goes the same i'll have to order native mellanox cable. I'll write you down the results. Thanks. Regards, Vadim. Vadim Alimov CIO Maximum-Net LLC vadim@alimov.net skype: vadim.alimov office: +38 044-374-04-51 ext. 601 cellular: +38 067-827-05-77 On 05/29/2015 05:32 PM, rondzierwa@comcast.net wrote: You seem to have gotten further than I did, I could not get a driver to recognize the card I was trying to use. Our current approach has been to switch to Solaris. Our options are more plentiful there, and coverage for various hardware seems more complete. >From your dmesg output, it looks like the ethernet device should be there. Try "ifconfig -a". You should see a new device called mlxen0: My plan was to hard configure the IB links in the rc.conf file like: ifconfig_mlxen0="inet 192.168.22.1 netmask 255.255.255.0" ron. ----- Original Message ----- From: "Vadim Alimov" To: freebsd-infiniband@freebsd.org Sent: Friday, May 29, 2015 7:05:35 AM Subject: Re: Does mlxen work on FreeBSD 10.1 with ConnectX-3 Hi. Did you manage to bring up a mellanox NIC with qsfp port as an ethernet device? I'm facing exactly the same issue. mlx4_core0: mem 0xfbd00000-0xfbdfffff,0xf9800000-0xf9ffffff irq 16 at device 0.0 on pci4 mlx4_core: Mellanox ConnectX core driver v2.1 (May 28 2015) mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.1 (May 28 2015) mlxen0: Ethernet address: 00:21:cc:49:48:93 mlx4_en: mlx4_core0: Port 1: Using 8 TX rings mlx4_en: mlx4_core0: Port 1: Using 8 RX rings Forward thanks for help. Vadim. -- Vadim Alimov CIO Maximum-Net LLC vadim@alimov.net skype: vadim.alimov office: +38 044-374-04-51 ext. 601 cellular: +38 067-827-05-77 _______________________________________________ freebsd-infiniband@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-infiniband To unsubscribe, send any mail to "freebsd-infiniband-unsubscribe@freebsd.org"