[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c1dfc28b01014bf3a46cb8acb83bd102@intel.com>
Date: Tue, 26 Jan 2021 00:39:28 +0000
From: "Saleem, Shiraz" <shiraz.saleem@...el.com>
To: Jason Gunthorpe <jgg@...dia.com>
CC: "dledford@...hat.com" <dledford@...hat.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Ertman, David M" <david.m.ertman@...el.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
Subject: RE: [PATCH 00/22] Add Intel Ethernet Protocol Driver for RDMA (irdma)
> Subject: Re: [PATCH 00/22] Add Intel Ethernet Protocol Driver for RDMA (irdma)
>
> On Fri, Jan 22, 2021 at 05:48:05PM -0600, Shiraz Saleem wrote:
> > From: "Shiraz, Saleem" <shiraz.saleem@...el.com>
> >
> > The following patch series introduces a unified Intel Ethernet
> > Protocol Driver for RDMA (irdma) for the X722 iWARP device and a new
> > E810 device which supports iWARP and RoCEv2. The irdma driver replaces
> > the legacy i40iw driver for X722 and extends the ABI already defined
> > for i40iw. It is backward compatible with legacy X722 rdma-core provider
> (libi40iw).
> >
> > X722 and E810 are PCI network devices that are RDMA capable. The RDMA
> > block of this parent device is represented via an auxiliary device exported to
> 'irdma'
> > using the core auxiliary bus infrastructure recently added for 5.11 kernel.
> > The parent PCI netdev drivers 'i40e' and 'ice' register auxiliary RDMA
> > devices with private data/ops encapsulated that bind to an 'irdma' auxiliary
> driver.
> >
> > This series is a follow on to an RFC series [1]. This series was built
> > against rdma for-next and currently includes the netdev patches for ease of
> review.
> > This include updates to 'ice' driver to provide RDMA support and converts 'i40e'
> > driver to use the auxiliary bus infrastructure .
> >
> > Once the patches are closer to merging, this series will be split into
> > a netdev-next and rdma-next patch series targeted at their respective
> > subsystems with Patch #1 and Patch #5 included in both. This is the
> > shared header file that will allow each series to independently compile.
> >
> > [1]
> > https://lore.kernel.org/linux-rdma/20200520070415.3392210-1-jeffrey.t.
> > kirsher@...el.com/
> >
> > Dave Ertman (4):
> > iidc: Introduce iidc.h
> > ice: Initialize RDMA support
> > ice: Implement iidc operations
> > ice: Register auxiliary device to provide RDMA
> >
> > Michael J. Ruhl (1):
> > RDMA/irdma: Add dynamic tracing for CM
> >
> > Mustafa Ismail (13):
> > RDMA/irdma: Register an auxiliary driver and implement private channel
> > OPs
> > RDMA/irdma: Implement device initialization definitions
> > RDMA/irdma: Implement HW Admin Queue OPs
> > RDMA/irdma: Add HMC backing store setup functions
> > RDMA/irdma: Add privileged UDA queue implementation
> > RDMA/irdma: Add QoS definitions
> > RDMA/irdma: Add connection manager
> > RDMA/irdma: Add PBLE resource manager
> > RDMA/irdma: Implement device supported verb APIs
> > RDMA/irdma: Add RoCEv2 UD OP support
> > RDMA/irdma: Add user/kernel shared libraries
> > RDMA/irdma: Add miscellaneous utility definitions
> > RDMA/irdma: Add ABI definitions
>
> I didn't check, but I will remind you to compile with make W=1 and ensure this is all
> clean. Lee is doing good work making RDMA clean for W=1.
>
Yes. That is done.
Powered by blists - more mailing lists