Message ID | 20240708080025.1593555-2-tariqt@nvidia.com (mailing list archive) |
---|---|
State | Changes Requested |
Delegated to: | Netdev Maintainers |
Headers | show |
Series | mlx5 misc patches 2023-07-08 | expand |
On Mon, 8 Jul 2024 11:00:16 +0300 Tariq Toukan wrote: > From: Daniel Jurgens <danielj@nvidia.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?
> From: Jakub Kicinski <kuba@kernel.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@nvidia.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.
On Wed, 10 Jul 2024 13:08:31 +0000 Dan Jurgens wrote: > > > 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 Makes sense, include in the commit message, please?
diff --git a/include/linux/mlx5/mlx5_ifc.h b/include/linux/mlx5/mlx5_ifc.h index fdad0071d599..360d42f041b0 100644 --- a/include/linux/mlx5/mlx5_ifc.h +++ b/include/linux/mlx5/mlx5_ifc.h @@ -1994,7 +1994,9 @@ struct mlx5_ifc_cmd_hca_cap_2_bits { u8 migration_tracking_state[0x1]; u8 reserved_at_ca[0x6]; u8 migration_in_chunks[0x1]; - u8 reserved_at_d1[0xf]; + u8 reserved_at_d1[0x1]; + u8 sf_eq_usage[0x1]; + u8 reserved_at_d3[0xd]; u8 cross_vhca_object_to_object_supported[0x20];