From: Jason Gunthorpe <jgg@mellanox.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Danit Goldberg <danitg@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Artemy Kovalyov <artemyko@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>
Subject: Re: [PATCH rdma-next] IB/mlx5: Report correctly tag matching rendezvous capability
Date: Fri, 5 Jul 2019 17:15:59 +0000 [thread overview]
Message-ID: <20190705171555.GH31525@mellanox.com> (raw)
In-Reply-To: <20190705162157.17336-1-leon@kernel.org>
On Fri, Jul 05, 2019 at 07:21:57PM +0300, Leon Romanovsky wrote:
> From: Danit Goldberg <danitg@mellanox.com>
>
> Tag matching with rendezvous offload for RC transport is controlled
> by FW and before this change, it was advertised to user as supported
> without any relation to FW.
>
> Separate tag matching for rendezvous and eager protocols, so users
> will see real capabilities.
>
> Cc: <stable@vger.kernel.org> # 4.13
> Fixes: eb761894351d ("IB/mlx5: Fill XRQ capabilities")
> Signed-off-by: Danit Goldberg <danitg@mellanox.com>
> Reviewed-by: Yishai Hadas <yishaih@mellanox.com>
> Reviewed-by: Artemy Kovalyov <artemyko@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> drivers/infiniband/hw/mlx5/main.c | 8 ++++++--
> include/rdma/ib_verbs.h | 4 ++--
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/infiniband/hw/mlx5/main.c b/drivers/infiniband/hw/mlx5/main.c
> index 07a05b0b9e42..c2a5780cb394 100644
> +++ b/drivers/infiniband/hw/mlx5/main.c
> @@ -1046,15 +1046,19 @@ static int mlx5_ib_query_device(struct ib_device *ibdev,
> }
>
> if (MLX5_CAP_GEN(mdev, tag_matching)) {
> - props->tm_caps.max_rndv_hdr_size = MLX5_TM_MAX_RNDV_MSG_SIZE;
> props->tm_caps.max_num_tags =
> (1 << MLX5_CAP_GEN(mdev, log_tag_matching_list_sz)) - 1;
> - props->tm_caps.flags = IB_TM_CAP_RC;
> props->tm_caps.max_ops =
> 1 << MLX5_CAP_GEN(mdev, log_max_qp_sz);
> props->tm_caps.max_sge = MLX5_TM_MAX_SGE;
> }
>
> + if (MLX5_CAP_GEN(mdev, tag_matching) &&
> + MLX5_CAP_GEN(mdev, rndv_offload_rc)) {
> + props->tm_caps.flags = IB_TM_CAP_RNDV_RC;
> + props->tm_caps.max_rndv_hdr_size = MLX5_TM_MAX_RNDV_MSG_SIZE;
> + }
> +
> if (MLX5_CAP_GEN(dev->mdev, cq_moderation)) {
> props->cq_caps.max_cq_moderation_count =
> MLX5_MAX_CQ_COUNT;
> diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h
> index 30eb68f36109..c5f8a9f17063 100644
> +++ b/include/rdma/ib_verbs.h
> @@ -308,8 +308,8 @@ struct ib_rss_caps {
> };
>
> enum ib_tm_cap_flags {
> - /* Support tag matching on RC transport */
> - IB_TM_CAP_RC = 1 << 0,
> + /* Support tag matching with rendezvous offload for RC transport */
> + IB_TM_CAP_RNDV_RC = 1 << 0,
> };
This is in the wrong header, right?
Jason
next prev parent reply other threads:[~2019-07-05 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 16:21 [PATCH rdma-next] IB/mlx5: Report correctly tag matching rendezvous capability Leon Romanovsky
2019-07-05 17:15 ` Jason Gunthorpe [this message]
2019-07-06 16:35 ` Leon Romanovsky
2019-07-08 17:26 ` Jason Gunthorpe
2019-07-08 17:39 ` 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=20190705171555.GH31525@mellanox.com \
--to=jgg@mellanox.com \
--cc=artemyko@mellanox.com \
--cc=danitg@mellanox.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=yishaih@mellanox.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