rdma-core

lp:rdma-core

  1. Git
  2. lp:rdma-core
Owned by Linux RDMA
Get this repository:
git clone https://git.launchpad.net/rdma-core

Import details

Import Status: Reviewed

This repository is an import of the Git repository at https://github.com/linux-rdma/rdma-core.git.

The next import is scheduled to run .

Last successful import was .

Import started on juju-98ee42-prod-launchpad-codeimport-5 and finished taking 50 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-1 and finished taking 1 minute — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-0 and finished taking 1 minute — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-4 and finished taking 30 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-0 and finished taking 2 minutes — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-1 and finished taking 50 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-0 and finished taking 50 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-5 and finished taking 50 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-5 and finished taking 30 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-5 and finished taking 30 seconds — see the log

Branches

Name Last Modified Last Commit
master 2024-04-15 18:07:59 UTC
Merge pull request #1448 from shefty/cmtime

Author: Leon Romanovsky
Author Date: 2024-04-15 18:07:59 UTC

Merge pull request #1448 from shefty/cmtime

librdmacm/cmtime: Rework of cmtime example
stable-v51 2024-04-02 11:32:37 UTC
stable branch creation

Author: Nicolas Morey
Author Date: 2024-04-02 11:31:37 UTC

stable branch creation

Add ABI files and tune Azure pipeline for changelog generation

Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v50 2024-04-02 11:31:10 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v49 2024-04-02 11:31:10 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v47 2024-04-02 11:31:09 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v48 2024-04-02 11:31:09 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v46 2024-04-02 11:31:07 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v45 2024-04-02 11:31:06 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v44 2024-04-02 11:31:01 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v43 2024-04-02 11:30:56 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v42 2024-04-02 11:30:51 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v41 2024-04-02 11:30:23 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v40 2024-04-02 11:30:18 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v39 2024-04-02 11:30:12 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v38 2024-04-02 11:30:06 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v37 2024-04-02 11:29:59 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v36 2024-04-02 11:29:52 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v35 2024-04-02 11:29:41 UTC
mlx5: DR, Using sq ts format when RoCE is disabled

Author: Itamar Gozlan
Author Date: 2024-03-10 17:00:36 UTC

mlx5: DR, Using sq ts format when RoCE is disabled

[ Upstream commit cebd491f520fbed90b19b01aad280bc43338ebaa ]

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 <igozlan@nvidia.com>
Signed-off-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v34 2024-03-20 12:23:56 UTC
librdmacm: adjust ECE function name in man page

Author: Honggang LI
Author Date: 2024-01-30 06:02:53 UTC

librdmacm: adjust ECE function name in man page

[ Upstream commit 1a302c7df2ad7851b8d5886c773f93a9370edc88 ]

Replace `ibv_get_ece()` with `ibv_query_ece()`.

Fixes: 97f8668eb53e ("librdmacm: Document ECE API")
Signed-off-by: Honggang LI <honggangli@163.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v33 2024-03-20 12:23:55 UTC
librdmacm: adjust ECE function name in man page

Author: Honggang LI
Author Date: 2024-01-30 06:02:53 UTC

librdmacm: adjust ECE function name in man page

[ Upstream commit 1a302c7df2ad7851b8d5886c773f93a9370edc88 ]

Replace `ibv_get_ece()` with `ibv_query_ece()`.

Fixes: 97f8668eb53e ("librdmacm: Document ECE API")
Signed-off-by: Honggang LI <honggangli@163.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v32 2024-03-20 12:23:53 UTC
librdmacm: adjust ECE function name in man page

Author: Honggang LI
Author Date: 2024-01-30 06:02:53 UTC

librdmacm: adjust ECE function name in man page

[ Upstream commit 1a302c7df2ad7851b8d5886c773f93a9370edc88 ]

Replace `ibv_get_ece()` with `ibv_query_ece()`.

Fixes: 97f8668eb53e ("librdmacm: Document ECE API")
Signed-off-by: Honggang LI <honggangli@163.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
stable-v31 2024-03-20 12:23:50 UTC
librdmacm: adjust ECE function name in man page

Author: Honggang LI
Author Date: 2024-01-30 06:02:53 UTC

librdmacm: adjust ECE function name in man page

[ Upstream commit 1a302c7df2ad7851b8d5886c773f93a9370edc88 ]

Replace `ibv_get_ece()` with `ibv_query_ece()`.

Fixes: 97f8668eb53e ("librdmacm: Document ECE API")
Signed-off-by: Honggang LI <honggangli@163.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
debian/unstable 2024-02-29 02:12:19 UTC
Release rdma-core 50.0-2

Author: Benjamin Drung
Author Date: 2024-02-29 02:12:19 UTC

Release rdma-core 50.0-2

Signed-off-by: Benjamin Drung <bdrung@ubuntu.com>
stable-v30 2024-01-22 13:59:32 UTC
Bump to version 30.12

Author: Nicolas Morey
Author Date: 2024-01-22 13:59:32 UTC

Bump to version 30.12

Signed-off-by: Nicolas Morey <nmorey@suse.com>
1 → 24 of 24 results First • Previous • Next • Last
This repository contains Public information 
Everyone can see this information.