[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<CH0PR12MB858029A605D7AF3849C54F6AC9A42@CH0PR12MB8580.namprd12.prod.outlook.com>
Date: Wed, 10 Jul 2024 13:08:31 +0000
From: Dan Jurgens <danielj@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>, Tariq Toukan <tariqt@...dia.com>
CC: "David S. Miller" <davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, Saeed Mahameed <saeedm@...dia.com>, Gal Pressman
<gal@...dia.com>, Leon Romanovsky <leonro@...dia.com>, William Tu
<witu@...dia.com>
Subject: RE: [PATCH net-next V2 01/10] net/mlx5: IFC updates for SF max IO EQs
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Tuesday, July 9, 2024 8:55 PM
> On Mon, 8 Jul 2024 11:00:16 +0300 Tariq Toukan wrote:
> > From: Daniel Jurgens <danielj@...dia.com>
> >
> > Expose a new cap sf_eq_usage. The vhca_resource_manager can write this
> > cap, indicating the SF driver should use max_num_eqs_24b to determine
> > how many EQs to use.
>
> How does vhca_resource_manager write this cap?
In most literal sense, MLX5_SET(cmd_hca_cap_2, hca_caps, sf_eq_usage, 1);.
But getting there flows through:
devlink port function set pci/0000:08:00.0/32768 max_io_eqs 32
See patch 02/10.
Powered by blists - more mailing lists