[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB4322B5ABE71F74F6D7B70D10DC929@BY5PR12MB4322.namprd12.prod.outlook.com>
Date: Tue, 9 Mar 2021 12:33:51 +0000
From: Parav Pandit <parav@...dia.com>
To: David Ahern <dsahern@...il.com>, ze wang <wangze712@...il.com>
CC: Saeed Mahameed <saeedm@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: mlx5 sub function issue
Hi David,
> From: David Ahern <dsahern@...il.com>
> Sent: Monday, March 8, 2021 9:18 PM
>
> On 3/8/21 12:21 AM, ze wang wrote:
> > mlxconfig tool from mft tools version 4.16.52 or higher to set number of SF.
> >
> > mlxconfig -d b3:00.0 PF_BAR2_ENABLE=0 PER_PF_NUM_SF=1
> > PF_SF_BAR_SIZE=8 mlxconfig -d b3:00.0 PER_PF_NUM_SF=1
> PF_TOTAL_SF=192
> > PF_SF_BAR_SIZE=8 mlxconfig -d b3:00.1 PER_PF_NUM_SF=1
> PF_TOTAL_SF=192
> > PF_SF_BAR_SIZE=8
> >
> > Cold reboot power cycle of the system as this changes the BAR size in
> > device
> >
>
> Is that capability going to be added to devlink?
Yes, want to expose as devlink resource at per controller level.
However devlink resource doesn’t have enough plumbing available to define controller, pf annotation which was the primary blocker for lacking this info right now.
Powered by blists - more mailing lists