[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210329160751.GE2356281@nvidia.com>
Date: Mon, 29 Mar 2021 13:07:51 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: "Saleem, Shiraz" <shiraz.saleem@...el.com>
Cc: Parav Pandit <parav@...dia.com>,
"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>,
"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 v2 05/23] ice: Add devlink params support
On Thu, Mar 25, 2021 at 08:10:13PM +0000, Saleem, Shiraz wrote:
> Maybe I am missing something but I see that a devlink hot reload is
> required to enforce the update? There isn't really a de-init
> required of PCI driver entities in this case for this rdma param.
> But only an unplug, plug of the auxdev with new value. Intuitively
> it feels more runtime-ish.
>
> There is also a device powerof2 requirement on the maxqp which I
> don't see enforceable as it stands.
>
> This is not super-critical for the initial submission but a nice to
> have. But I do want to brainstorm options..
devlink upai often seems to be an adventure, can you submit this
driver without devlink (or any other uapis) then debate how to add
them in as followup patches?
Jason
Powered by blists - more mailing lists