[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1da3385c7115c57fabd5c932033e893e5efc7e79.camel@nvidia.com>
Date: Wed, 15 Dec 2021 22:15:10 +0000
From: Saeed Mahameed <saeedm@...dia.com>
To: "kuba@...nel.org" <kuba@...nel.org>
CC: Parav Pandit <parav@...dia.com>, Jiri Pirko <jiri@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
Sunil Sudhakar Rani <sunrani@...dia.com>,
Bodong Wang <bodong@...dia.com>
Subject: Re: [PATCH net-next 1/2] devlink: Add support to set port function as
trusted
On Wed, 2021-12-15 at 11:22 -0800, Jakub Kicinski wrote:
> On Wed, 15 Dec 2021 18:19:16 +0000 Saeed Mahameed wrote:
> > After some internal discussions, the plan is to not push new
> > interfaces, but to utilize the existing devlink params interface
> > for
> > devlink port functions.
> >
> > We will suggest a more fine grained parameters to control a port
> > function (SF/VF) well-defined capabilities.
> >
> > devlink port function param set/get DEV/PORT_INDEX name PARAMETER
> > value
> > VALUE cmode { runtime | driverinit | permanent }
> >
> > Jiri is already on-board. Jakub I hope you are ok with this, let us
> > know if you have any concerns before we start implementation.
>
> You can use mail pigeon to configure this, my questions were about
> the feature itself not the interface.
We will have a parameter per feature we want to enable/disable instead
of a global "trust" knob.
Powered by blists - more mailing lists