From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Lior Nahmanson <liorna@nvidia.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Meir Lichtinger <meirl@nvidia.com>
Subject: [PATCH rdma-next] RDMA/mlx5: Relax DCS QP creation checks
Date: Mon, 30 Aug 2021 13:48:49 +0300 [thread overview]
Message-ID: <3e7b3363fd73686176cc584295e86832a7cf99b2.1630320354.git.leonro@nvidia.com> (raw)
From: Lior Nahmanson <liorna@nvidia.com>
In order to create DCS QPs, we don't need to rely on both
log_max_dci_stream_channels and log_max_dci_errored_streams capabilities.
Fixes: 11656f593a86 ("RDMA/mlx5: Add DCS offload support")
Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
---
Jason,
Please add this patch in the upcoming PR for the feature that was
accepted in this cycle.
Thanks
---
drivers/infiniband/hw/mlx5/qp.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/infiniband/hw/mlx5/qp.c b/drivers/infiniband/hw/mlx5/qp.c
index 81e3170a1ae6..4e2d0f8f267f 100644
--- a/drivers/infiniband/hw/mlx5/qp.c
+++ b/drivers/infiniband/hw/mlx5/qp.c
@@ -2813,8 +2813,7 @@ static int process_vendor_flags(struct mlx5_ib_dev *dev, struct mlx5_ib_qp *qp,
process_vendor_flag(dev, &flags, MLX5_QP_FLAG_TYPE_DCI, true, qp);
process_vendor_flag(dev, &flags, MLX5_QP_FLAG_TYPE_DCT, true, qp);
process_vendor_flag(dev, &flags, MLX5_QP_FLAG_DCI_STREAM,
- MLX5_CAP_GEN(mdev, log_max_dci_stream_channels) &&
- MLX5_CAP_GEN(mdev, log_max_dci_errored_streams),
+ MLX5_CAP_GEN(mdev, log_max_dci_stream_channels),
qp);
process_vendor_flag(dev, &flags, MLX5_QP_FLAG_SIGNATURE, true, qp);
--
2.31.1
next reply other threads:[~2021-08-30 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 10:48 Leon Romanovsky [this message]
2021-08-30 12:48 ` [PATCH rdma-next] RDMA/mlx5: Relax DCS QP creation checks Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e7b3363fd73686176cc584295e86832a7cf99b2.1630320354.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=liorna@nvidia.com \
--cc=meirl@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).