Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Wenpeng Liang <liangwenpeng@huawei.com>
To: <jgg@nvidia.com>, <leon@kernel.org>
Cc: <linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>,
	<liangwenpeng@huawei.com>
Subject: [PATCH for-next 0/4] RDMA/hns: Add more restrack attributes to hns driver
Date: Mon, 24 Jan 2022 20:46:20 +0800	[thread overview]
Message-ID: <20220124124624.55352-1-liangwenpeng@huawei.com> (raw)

First refactored the restrack code of the driver, and then added more
restrack attributes.

Wenpeng Liang (4):
  RDMA/hns: Refactor the restrack code of CQ
  RDMA/hns: Add more restrack attributes to CQ
  RDMA/hns: Add support for QP's restrack attributes
  RDMA/hns: Add support for MR's restrack attributes

 drivers/infiniband/hw/hns/Makefile            |   2 +-
 drivers/infiniband/hw/hns/hns_roce_device.h   |  13 +-
 drivers/infiniband/hw/hns/hns_roce_hw_v2.c    |  79 ++++-
 drivers/infiniband/hw/hns/hns_roce_hw_v2.h    |  30 --
 .../infiniband/hw/hns/hns_roce_hw_v2_dfx.c    |  35 ---
 drivers/infiniband/hw/hns/hns_roce_main.c     |   2 +
 drivers/infiniband/hw/hns/hns_roce_restrack.c | 272 ++++++++++++++----
 7 files changed, 288 insertions(+), 145 deletions(-)
 delete mode 100644 drivers/infiniband/hw/hns/hns_roce_hw_v2_dfx.c

--
2.33.0


             reply	other threads:[~2022-01-24 12:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 12:46 Wenpeng Liang [this message]
2022-01-24 12:46 ` [PATCH for-next 1/4] RDMA/hns: Refactor the restrack code of CQ Wenpeng Liang
2022-01-24 12:46 ` [PATCH for-next 2/4] RDMA/hns: Add more restrack attributes to CQ Wenpeng Liang
2022-01-24 12:46 ` [PATCH for-next 3/4] RDMA/hns: Add support for QP's restrack attributes Wenpeng Liang
2022-01-25  8:28   ` Leon Romanovsky
2022-01-27  1:29     ` Wenpeng Liang
2022-01-24 12:46 ` [PATCH for-next 4/4] RDMA/hns: Add support for MR's " Wenpeng Liang

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=20220124124624.55352-1-liangwenpeng@huawei.com \
    --to=liangwenpeng@huawei.com \
    --cc=jgg@nvidia.com \
    --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