From: Jason Gunthorpe <jgg@nvidia.com>
To: Weihang Li <liweihang@huawei.com>
Cc: <dledford@redhat.com>, <leon@kernel.org>,
<linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH for-next 7/8] RDMA/hns: Add UD support for HIP09
Date: Thu, 12 Nov 2020 14:35:32 -0400 [thread overview]
Message-ID: <20201112183532.GA964096@nvidia.com> (raw)
In-Reply-To: <1604057975-23388-8-git-send-email-liweihang@huawei.com>
On Fri, Oct 30, 2020 at 07:39:34PM +0800, Weihang Li wrote:
> HIP09 supports service type of Unreliable Datagram, add necessary process
> to enable this feature.
>
> Signed-off-by: Weihang Li <liweihang@huawei.com>
> drivers/infiniband/hw/hns/hns_roce_device.h | 2 ++
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 8 +++++---
> drivers/infiniband/hw/hns/hns_roce_qp.c | 3 ++-
> 3 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/infiniband/hw/hns/hns_roce_device.h b/drivers/infiniband/hw/hns/hns_roce_device.h
> index 9a032d0..23f8fe7 100644
> +++ b/drivers/infiniband/hw/hns/hns_roce_device.h
> @@ -222,7 +222,9 @@ enum {
> HNS_ROCE_CAP_FLAG_FRMR = BIT(8),
> HNS_ROCE_CAP_FLAG_QP_FLOW_CTRL = BIT(9),
> HNS_ROCE_CAP_FLAG_ATOMIC = BIT(10),
> + HNS_ROCE_CAP_FLAG_UD = BIT(11),
Why add this flag if nothing reads it?
> HNS_ROCE_CAP_FLAG_SDI_MODE = BIT(14),
> +
> };
Extra space
If I recall properly earlier chips did not have a GID table so could
not support UD because they could not secure the AH, or something like
that.
So, I would expect to see that only the new devices support UD, but
I can't quite see that in this patch??
Jason
next prev parent reply other threads:[~2020-11-12 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 11:39 [PATCH for-next 0/8] RDMA/hns: Support UD for HIP09 Weihang Li
2020-10-30 11:39 ` [PATCH for-next 1/8] RDMA/hns: Only record vlan info for HIP08 Weihang Li
2020-10-30 11:39 ` [PATCH for-next 2/8] RDMA/hns: Fix missing fields in address vector Weihang Li
2020-10-30 11:39 ` [PATCH for-next 3/8] RDMA/hns: Avoid setting loopback indicator when smac is same as dmac Weihang Li
2020-10-30 11:39 ` [PATCH for-next 4/8] RDMA/hns: Add check for the validity of sl configuration in UD SQ WQE Weihang Li
2020-11-12 18:32 ` Jason Gunthorpe
2020-11-14 3:46 ` liweihang
2020-11-16 16:09 ` Jason Gunthorpe
2020-11-17 6:42 ` liweihang
2020-10-30 11:39 ` [PATCH for-next 5/8] RDMA/hns: Remove the portn field " Weihang Li
2020-10-30 11:39 ` [PATCH for-next 6/8] RDMA/hns: Simplify process of filling " Weihang Li
2020-10-30 11:39 ` [PATCH for-next 7/8] RDMA/hns: Add UD support for HIP09 Weihang Li
2020-11-12 18:35 ` Jason Gunthorpe [this message]
2020-11-14 2:43 ` liweihang
2020-10-30 11:39 ` [PATCH for-next 8/8] RDMA/hns: Add support for UD inline Weihang Li
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=20201112183532.GA964096@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liweihang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.