Files
linux-bredos/include/linux
Or Har-Toov 0c5275bf75 RDMA/mlx5: Use sq timestamp as QP timestamp when RoCE is disabled
When creating a QP, one of the attributes is TS format (timestamp).
In some devices, we have a limitation that all QPs should have the same
ts_format. The ts_format is chosen based on the device's capability.
The qp_ts_format cap resides under the RoCE caps table, and the
cap will be 0 when RoCE is disabled. So when RoCE is disabled, the
value that should be queried is sq_ts_format under HCA caps.

Consider the case when the system supports REAL_TIME_TS format (0x2),
some QPs are created with REAL_TIME_TS as ts_format, and afterwards
RoCE gets disabled. When trying to construct a new QP, we can't use
the qp_ts_format, that is queried from the RoCE caps table, Since it
leads to passing 0x0 (FREE_RUNNING_TS) as the value of the qp_ts_format,
which is different than the ts_format of the previously allocated
QPs REAL_TIME_TS format (0x2).

Thus, to resolve this, read the sq_ts_format, which also reflect
the supported ts format for the QP when RoCE is disabled.

Fixes: 4806f1e2fe ("net/mlx5: Set QP timestamp mode to default")
Signed-off-by: Maher Sanalla <msanalla@nvidia.com>
Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
Link: https://lore.kernel.org/r/32801966eb767c7fd62b8dea3b63991d5fbfe213.1718554199.git.leon@kernel.org
Reviewed-by: Simon Horman <horms@kernel.org>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
2024-06-26 10:53:29 -03:00
..
2024-03-19 16:11:42 +01:00
2024-04-24 11:06:26 -07:00
2024-04-25 20:55:49 -07:00
2024-05-02 20:35:57 +02:00
2024-04-17 08:44:03 -06:00
2024-03-11 15:37:23 -07:00
2024-04-29 16:28:07 -07:00
2024-05-08 17:29:22 -04:00
2024-04-23 09:03:37 +09:00
2024-05-05 17:53:55 -07:00
2024-03-12 23:08:29 -07:00
2024-05-11 00:41:15 +00:00
2024-04-15 16:03:24 -04:00
2024-05-09 13:02:39 +02:00
2024-05-19 14:36:17 -07:00
2024-05-22 16:12:48 -07:00
2024-05-19 14:40:44 -07:00
2024-04-23 13:16:03 +02:00
2024-05-23 13:38:15 +02:00
2024-06-05 19:19:26 -07:00
2024-05-03 10:44:42 +01:00
2024-04-15 14:31:48 +02:00
2024-05-05 17:53:49 -07:00
2024-05-05 17:53:50 -07:00
2024-03-26 11:07:20 -07:00
2024-03-13 12:53:53 -07:00
2024-03-13 12:53:53 -07:00
2024-04-15 19:43:48 +02:00
2024-04-02 18:03:32 -07:00
2024-04-03 09:59:38 +01:00
2024-05-02 16:28:15 +02:00
2024-04-09 10:53:44 +02:00
2024-03-26 09:01:18 +01:00
2024-05-04 18:57:21 +02:00
2024-05-23 19:40:26 -07:00
2024-04-08 11:49:02 +01:00
2024-05-06 12:05:00 +02:00
2024-04-07 02:42:36 -04:00
2024-04-25 20:55:48 -07:00