diff options
| author | Maher Sanalla <msanalla@nvidia.com> | 2022-02-16 11:01:04 +0200 |
|---|---|---|
| committer | Saeed Mahameed <saeedm@nvidia.com> | 2022-02-23 16:08:12 -0800 |
| commit | 7f839965b2d77e1926ad08b23c51d60988f10a99 (patch) | |
| tree | 8b5aa300078d20c691c9bf4a7af871e72425e694 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | ecd9c5cd46e013659e2fad433057bad1ba66888e (diff) | |
net/mlx5: Update log_max_qp value to be 17 at most
Currently, log_max_qp value is dependent on what FW reports as its max capability.
In reality, due to a bug, some FWs report a value greater than 17, even though they
don't support log_max_qp > 17.
This FW issue led the driver to exhaust memory on startup.
Thus, log_max_qp value is set to be no more than 17 regardless
of what FW reports, as it was before the cited commit.
Fixes: f79a609ea6bf ("net/mlx5: Update log_max_qp value to FW max capability")
Signed-off-by: Maher Sanalla <msanalla@nvidia.com>
Reviewed-by: Avihai Horon <avihaih@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions