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@openeuler.org>
Subject: Re: [PATCH v3 for-next] RDMA/hns: Adjust definition of FRMR fields
Date: Wed, 10 Feb 2021 14:21:33 -0400 [thread overview]
Message-ID: <20210210182133.GA1470084@nvidia.com> (raw)
In-Reply-To: <1612924424-28217-1-git-send-email-liweihang@huawei.com>
On Wed, Feb 10, 2021 at 10:33:44AM +0800, Weihang Li wrote:
> From: Yixing Liu <liuyixing1@huawei.com>
>
> FRMR is not well-supported on HIP08, it is re-designed for HIP09 and the
> position of related fields is changed. Then the ULPs should be forbidden to
> use FRMR on older hardwares.
>
> Signed-off-by: Yixing Liu <liuyixing1@huawei.com>
> Signed-off-by: Weihang Li <liweihang@huawei.com>
> ---
> This patch is one of series "RDMA/hns: Updates for 5.12", the others have
> been applied.
>
> Changes since v2:
> * Aovid setting IB_DEVICE_MEM_MGT_EXTENSIONS for HIP08 or older hardwares.
> * Link: https://patchwork.kernel.org/project/linux-rdma/patch/1612859923-44041-1-git-send-email-liweihang@huawei.com/
>
> Changes since v1:
> * Add check for HW version and rewrite the description.
> * Link: https://patchwork.kernel.org/project/linux-rdma/patch/1612517974-31867-6-git-send-email-liweihang@huawei.com/
>
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 45 +++++++++++++++++-------------
> drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 12 ++++----
> drivers/infiniband/hw/hns/hns_roce_main.c | 3 +-
> 3 files changed, 34 insertions(+), 26 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-02-10 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 2:33 [PATCH v3 for-next] RDMA/hns: Adjust definition of FRMR fields Weihang Li
2021-02-10 18:21 ` Jason Gunthorpe [this message]
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=20210210182133.GA1470084@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--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.