[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM8PR12MB548045DA5FE443656466CE6CDC5A9@DM8PR12MB5480.namprd12.prod.outlook.com>
Date: Thu, 20 Jan 2022 06:19:20 +0000
From: Parav Pandit <parav@...dia.com>
To: Saeed Mahameed <saeedm@...dia.com>
CC: Jakub Kicinski <kuba@...nel.org>,
Saeed Mahameed <saeed@...nel.org>,
Sunil Sudhakar Rani <sunrani@...dia.com>,
Jiri Pirko <jiri@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
Bodong Wang <bodong@...dia.com>
Subject: RE: [PATCH net-next 1/2] devlink: Add support to set port function as
trusted
> From: Saeed Mahameed <saeedm@...dia.com>
> Sent: Thursday, January 20, 2022 11:34 AM
>
> On 20 Jan 04:52, Parav Pandit wrote:
> >
> >> From: Saeed Mahameed <saeedm@...dia.com>
> >> Sent: Thursday, January 20, 2022 6:11 AM
> >
> >[..]
> >> >
> >> >I do agree you and Saeed that instead of port function param, port
> >> >function
> >> resource is more suitable here even though its bool.
> >> >
> >>
> >> I believe flexibility can be achieved with some FW message? Parav can
> >> you investigate ? To be clear here the knob must be specific to
> >> sw_steering exposed as memory resource.
> >>
> >Sure.
> >I currently think of user interface something like below, I will get
> >back with more plumbing of netlink and enum/string.
> >
> ># to enable
> >devlink port function resource set pci/0000:03:00.0/port_index
> >device_memory/sw_steering 1
> >
>
> this looks like an abuse of the interface, I literally meant to control the amount
> of ICM pages dedicated for SW steering per function, this requires some FW
> support, but i think this is the correct direction.
Ok. I will evaluate and update.
>
> ># to disable
> >devlink port function resource set pci/0000:03:00.0/port_index
> >device_memory/sw_steering 0 (current default)
> >
> >Thanks Jakub, Saeed for the inputs and direction.
Powered by blists - more mailing lists