From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Talpey Subject: Re: [PATCH v6 01/26] IB/Verbs: Implement new callback query_transport() Date: Fri, 24 Apr 2015 10:46:35 -0400 Message-ID: <553A574B.80208@talpey.com> References: <1429878230-11749-1-git-send-email-yun.wang@profitbricks.com> <1429878230-11749-2-git-send-email-yun.wang@profitbricks.com> <553A5362.3040808@talpey.com> <553A54BB.4080902@profitbricks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <553A54BB.4080902@profitbricks.com> Sender: linux-kernel-owner@vger.kernel.org To: Michael Wang , Roland Dreier , Sean Hefty , Hal Rosenstock , linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Steve Wise , Jason Gunthorpe , Doug Ledford , Ira Weiny , Tom Tucker , Hoang-Nam Nguyen , Christoph Raisch , Mike Marciniszyn , Eli Cohen , Faisal Latif , Jack Morgenstein , Or Gerlitz , Haggai Eran List-Id: linux-rdma@vger.kernel.org On 4/24/2015 10:35 AM, Michael Wang wrote: > > > On 04/24/2015 04:29 PM, Tom Talpey wrote: >> On 4/24/2015 8:23 AM, Michael Wang wrote: > [snip] >>> +static enum rdma_transport_type >>> +mlx5_ib_query_transport(struct ib_device *device, u8 port_num) >>> +{ >>> + return RDMA_TRANSPORT_IB; >>> +} >>> + >> >> >> Just noticed that mlx5 is not being coded as RoCE-capable like mlx4. >> The mlx5 driver is for the new ConnectX-4, which implements all thre= e >> of IB, RoCE and RoCEv2, right? Are those last two not supported? > > I'm not sure about the details of mlx5, but according to the current > implementation, it's transport is IB without a link-layer callback, > which means it doesn't support IBoE... > > And there is no method to change the port link-layer type as mlx4 did= =2E Hal, is that correct? From the Mellanox web: http://www.mellanox.com/related-docs/products/IB_Adapter_card_brochure_= c_2_3.pdf "ConnectX-4 ConnectX-4 adapter cards with Virtual Protocol Interconnect (VPI), supporting EDR 100Gb/s InfiniBand and 100Gb/s Ethernet connectivity, provide the... "Virtual Protocol Interconnect VPI=AE flexibility enables any standard networking, clustering, storage= , and management protocol to seamlessly operate over any converged networ= k leveraging a consolidated software stack. Each port can operate on InfiniBand, Ethernet, or Data Center Bridging (DCB) fabrics, and supports IP over InfiniBand (IPoIB), Ethernet over InfiniBand (EoIB) and RDMA over Converged Ethernet (RoCE and RoCEv2).