When creating a QP in SW steering, 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 qp_ts_format cap resides under the RoCE caps table, and the cap is
not queried when RoCE is disabled.
Consider the case when the system is configured to run with REAL_TIME_TS
format (0x2), some QPs are created, and we disable RoCE.
When trying to construct a new QP, we can't use the qp_ts_format, that
is queried from the RoCE caps table.
That leads to passing 0x0 (FREE_RUNNING_TS) as the value of the
qp_ts_format, which is different than the ts_format of the previous QPs
REAL_TIME_TS format (0x2) and the creation will fail.
To resolve this, we will read the sq_ts_format, which also reflect the
supported ts format for the QP when RoCE is disabled, and override it
with qp_ts_format from the RoCE caps table if RoCE is enabled.
Fixes: ed504ab47384 ("mlx5: DR, Set QP timestamp mode to default")
Signed-off-by: Itamar Gozlan <email address hidden>
Signed-off-by: Alex Vesker <email address hidden>
Signed-off-by: Yishai Hadas <email address hidden>
Signed-off-by: Nicolas Morey <email address hidden>
Fix the error flow of qelr_alloc_context() by making sure to free the
allocated resources.
Fixes: cae4a99ae679 ("libqedr: add support for XRC-SRQ's.")
Signed-off-by: Kamal Heib <email address hidden>
Signed-off-by: Nicolas Morey <email address hidden>
2909210...
by
Nicolas Morey <email address hidden>
Bump to version 47.2
Signed-off-by: Nicolas Morey <email address hidden>
5d2cd85...
by
Hamdan Igbaria <email address hidden>
mlx5: DR, Fix ASO CT action applying in cross domain
Fix ASO CT action applying in cross domain, instead of checking if the
GVMI's of the domains are different, check if the domains are different,
since we can have both domains on the same GVMI.
This fix will allow two different domains on the same GVMI to share the
same ASO CT action.
For FDB sample flow, the termination table on sample destination path
must go to the eswitch manager vport. On BlueField, the eswitch manager
vport is 0xfffe rather than 0.
Change to set the correct destination vport depends on the current
eswitch function is ECPF or PF.
Fixes: 161d5ad37556 ("mlx5: DR, Add support for destination array action")
Signed-off-by: Jiawei Wang <email address hidden>
Reviewed-by: Hamdan Igbaria <email address hidden>
Signed-off-by: Yishai Hadas <email address hidden>
Signed-off-by: Nicolas Morey <email address hidden>
6b608a5...
by
Yevgeny Kliteynik <email address hidden>
Go-To-Vport action on RX is not allowed when the vport is uplink. If
this happens on RX domain, the rule insertion fails, as the rule is
illegal.
If this happens on RX side of the FDB domain, then the TX part of the
rule is legal, and the RX part will be replaced with drop.
When FW provides ICM addresses for drop RX/TX, the provided capability
is 64 bits that contain its GVMI as well as the ICM address itself. In
case of TX DROP this GVMI is different from the GVMI that the domain is
operating on.
This patch fixes the action to use this GVMI ID, as provided by FW.
