[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <PH0PR12MB54819BFE1033C88504D5B256DCF79@PH0PR12MB5481.namprd12.prod.outlook.com>
Date: Tue, 10 Aug 2021 11:59:32 +0000
From: Parav Pandit <parav@...dia.com>
To: Parav Pandit <parav@...dia.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next 00/10] devlink: Control auxiliary devices
> From: Parav Pandit <parav@...dia.com>
> Sent: Tuesday, August 10, 2021 5:16 PM
> Hi Dave, Jakub,
>
> Currently, for mlx5 multi-function device, a user is not able to control which
> functionality to enable/disable. For example, each PCI PF, VF, SF function by
> default has netdevice, RDMA and vdpa-net devices always enabled.
>
> Hence, enable user to control which device functionality to enable/disable.
>
> This is achieved by using existing devlink params [1] to enable/disable eth,
> rdma and vdpa net functionality control knob.
>
> For example user interested in only vdpa device function: performs,
>
> $ devlink dev param set pci/0000:06:00.0 name enable_rdma value false \
> cmode driverinit
> $ devlink dev param set pci/0000:06:00.0 name enable_eth value false \
> cmode driverinit
> $ devlink dev param set pci/0000:06:00.0 name enable_vnet value true \
> cmode driverinit
I missed to CC rdma and virt mailing list.
I am resending the series to CC them.
Powered by blists - more mailing lists