diff options
| author |   Maher Sanalla <msanalla@nvidia.com> | 2022-01-05 14:50:11 +0200 |
|---|---|---|
| committer |   Saeed Mahameed <saeedm@nvidia.com> | 2022-01-06 16:22:52 -0800 |
| commit | f79a609ea6bf54ad2d2c24e4de4524288b221666 (patch) | |
| tree | 05b13df8576ebe6b6b63920935691e29ed9111fe /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | net/mlx5: SF, Use all available cpu for setting cpu affinity (diff) | |
| download | wireguard-linux-f79a609ea6bf54ad2d2c24e4de4524288b221666.tar.xz wireguard-linux-f79a609ea6bf54ad2d2c24e4de4524288b221666.zip | |
net/mlx5: Update log_max_qp value to FW max capability
log_max_qp in driver's default profile #2 was set to 18, but FW actually
supports 17 at the most - a situation that led to the concerning print
when the driver is loaded:
"log_max_qp value in current profile is 18, changing to HCA capabaility
limit (17)"
The expected behavior from mlx5_profile #2 is to match the maximum FW
capability in regards to log_max_qp. Thus, log_max_qp in profile #2 is
initialized to a defined static value (0xff) - which basically means that
when loading this profile, log_max_qp value will be what the currently
installed FW supports at most.
Signed-off-by: Maher Sanalla <msanalla@nvidia.com>
Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions