[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210201191952.GP4247@nvidia.com>
Date: Mon, 1 Feb 2021 15:19:52 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: "Saleem, Shiraz" <shiraz.saleem@...el.com>
CC: Leon Romanovsky <leon@...nel.org>,
"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>,
"Ismail, Mustafa" <mustafa.ismail@...el.com>
Subject: Re: [PATCH 07/22] RDMA/irdma: Register an auxiliary driver and
implement private channel OPs
On Sat, Jan 30, 2021 at 01:19:22AM +0000, Saleem, Shiraz wrote:
> Do you mean 2 different auxiliary device names - one for RoCE and
> iWARP? The drv.probe() and other callbacks will be very similar for
> gen2, so one gen2 aux driver which can bind to iW and RoCE aux
> device should suffice.
You probably end up with three aux device names, gen 1, gen 2 roce and
gen 2 iwarp
Certainly flipping modes should change the device name. This helps
keep everything synchronized, since you delete a device and wait for
all drivers to unbind then create a new device with a different
name.
Jason
Powered by blists - more mailing lists