From: Weihang Li <liweihang@huawei.com>
To: <dledford@redhat.com>, <jgg@ziepe.ca>
Cc: <leon@kernel.org>, <linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: [PATCH for-next 0/7] RDMA/hns: Refactor qp related code
Date: Mon, 20 Jan 2020 16:19:30 +0800 [thread overview]
Message-ID: <1579508377-55818-1-git-send-email-liweihang@huawei.com> (raw)
This series refactor qp related code, including creating, destroying qp and
so on to make the processs easier to understand and maintain.
Xi Wang (7):
RDMA/hns: Optimize qp destroy flow
RDMA/hns: Optimize qp context create and destroy flow
RDMA/hns: Optimize qp number assign flow
RDMA/hns: Optimize qp buffer allocation flow
RDMA/hns: Optimize qp param setup flow
RDMA/hns: Optimize kernel qp wrid allocation flow
RDMA/hns: Optimize qp doorbell allocation flow
drivers/infiniband/hw/hns/hns_roce_device.h | 6 +-
drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 19 +-
drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 43 +-
drivers/infiniband/hw/hns/hns_roce_qp.c | 755 ++++++++++++++++------------
4 files changed, 431 insertions(+), 392 deletions(-)
--
2.8.1
next reply other threads:[~2020-01-20 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 8:19 Weihang Li [this message]
2020-01-20 8:19 ` [PATCH for-next 1/7] RDMA/hns: Optimize qp destroy flow Weihang Li
2020-01-20 8:19 ` [PATCH for-next 2/7] RDMA/hns: Optimize qp context create and " Weihang Li
2020-01-20 8:19 ` [PATCH for-next 3/7] RDMA/hns: Optimize qp number assign flow Weihang Li
2020-01-20 8:19 ` [PATCH for-next 4/7] RDMA/hns: Optimize qp buffer allocation flow Weihang Li
2020-01-23 14:31 ` Leon Romanovsky
2020-01-23 22:55 ` Jason Gunthorpe
2020-01-26 8:35 ` Weihang Li
2020-01-20 8:19 ` [PATCH for-next 5/7] RDMA/hns: Optimize qp param setup flow Weihang Li
2020-01-20 8:19 ` [PATCH for-next 6/7] RDMA/hns: Optimize kernel qp wrid allocation flow Weihang Li
2020-01-20 8:19 ` [PATCH for-next 7/7] RDMA/hns: Optimize qp doorbell " 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=1579508377-55818-1-git-send-email-liweihang@huawei.com \
--to=liweihang@huawei.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@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