From: "Wei Hu (Xavier)" <xavier.huwei@huawei.com>
To: <dledford@redhat.com>, <jgg@ziepe.ca>
Cc: <linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>,
<linux-kernel@vger.kernel.org>, <shaobo.xu@intel.com>,
<xavier.huwei@tom.com>, <zhangxiping3@huawei.com>
Subject: [PATCH V2 rdma-rc 0/3] RDMA/hns: Bug fixes in hns RoCE driver
Date: Tue, 28 Nov 2017 15:10:25 +0800 [thread overview]
Message-ID: <1511853028-35191-1-git-send-email-xavier.huwei@huawei.com> (raw)
This patch-set introduces three patches to fix the memory related
issues. one fixes DMA operation failure when smmu is enabled.
the other two patches fixes incorrect usage of dma API that may
cause coherency problems.
Wei Hu (Xavier) (3):
RDMA/hns: Fix the issue of IOVA not page continuous in hip08
RDMA/hns: Get rid of virt_to_page and vmap calls after
dma_alloc_coherent
RDMA/hns: Get rid of page operation after dma_alloc_coherent
drivers/infiniband/hw/hns/hns_roce_alloc.c | 23 -----------------------
drivers/infiniband/hw/hns/hns_roce_device.h | 4 +---
drivers/infiniband/hw/hns/hns_roce_hem.c | 25 +++++++++++++------------
drivers/infiniband/hw/hns/hns_roce_hem.h | 1 +
drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 22 +++++++++++++++-------
5 files changed, 30 insertions(+), 45 deletions(-)
--
1.9.1
next reply other threads:[~2017-11-28 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 7:10 Wei Hu (Xavier) [this message]
2017-11-28 7:10 ` [PATCH V2 rdma-rc 1/3] RDMA/hns: Fix the issue of IOVA not page continuous in hip08 Wei Hu (Xavier)
2017-11-28 7:10 ` [PATCH V2 rdma-rc 2/3] RDMA/hns: Get rid of virt_to_page and vmap calls after dma_alloc_coherent Wei Hu (Xavier)
2017-11-28 7:10 ` [PATCH V2 rdma-rc 3/3] RDMA/hns: Get rid of page operation " Wei Hu (Xavier)
2017-12-02 0:04 ` [PATCH V2 rdma-rc 0/3] RDMA/hns: Bug fixes in hns RoCE driver 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=1511853028-35191-1-git-send-email-xavier.huwei@huawei.com \
--to=xavier.huwei@huawei.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=shaobo.xu@intel.com \
--cc=xavier.huwei@tom.com \
--cc=zhangxiping3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®