From: sharmaajay@linuxonhyperv.com
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Dexuan Cui <decui@microsoft.com>, Wei Liu <wei.liu@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: linux-rdma@vger.kernel.org, linux-hyperv@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Ajay Sharma <sharmaajay@microsoft.com>
Subject: [Patch v3 0/4] RDMA/mana_ib Read Capabilities
Date: Wed, 26 Jul 2023 13:08:20 -0700 [thread overview]
Message-ID: <1690402104-29518-1-git-send-email-sharmaajay@linuxonhyperv.com> (raw)
From: Ajay Sharma <sharmaajay@microsoft.com>
This patch series introduces some cleanup changes and
resource control changes. The mana and mana_ib devices
are used at common places so a consistent naming is
introduced. Adapter object container to have a common
point of object release for resources and query the
management software to prevent resource overflow.
It also introduces async channel for management to
notify the clients in case of errors/info.
Ajay Sharma (4):
RDMA/mana_ib : Rename all mana_ib_dev type variables to mib_dev
RDMA/mana_ib : Register Mana IB device with Management SW
RDMA/mana_ib : Create adapter and Add error eq
RDMA/mana_ib : Query adapter capabilities
drivers/infiniband/hw/mana/cq.c | 12 +-
drivers/infiniband/hw/mana/device.c | 72 +++--
drivers/infiniband/hw/mana/main.c | 282 +++++++++++++-----
drivers/infiniband/hw/mana/mana_ib.h | 96 +++++-
drivers/infiniband/hw/mana/mr.c | 42 ++-
drivers/infiniband/hw/mana/qp.c | 82 ++---
drivers/infiniband/hw/mana/wq.c | 21 +-
.../net/ethernet/microsoft/mana/gdma_main.c | 151 ++++++----
drivers/net/ethernet/microsoft/mana/mana_en.c | 3 +
include/net/mana/gdma.h | 16 +-
10 files changed, 529 insertions(+), 248 deletions(-)
--
2.25.1
next reply other threads:[~2023-07-26 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 20:08 sharmaajay [this message]
2023-07-26 20:08 ` [Patch v3 1/4] RDMA/mana_ib : Rename all mana_ib_dev type variables to mib_dev sharmaajay
2023-07-28 3:02 ` [EXTERNAL] " Ajay Sharma
2023-07-28 21:23 ` Long Li
2023-07-26 20:08 ` [Patch v3 2/4] RDMA/mana_ib : Register Mana IB device with Management SW sharmaajay
2023-07-28 3:01 ` [EXTERNAL] " Ajay Sharma
2023-07-28 21:32 ` Long Li
2023-07-26 20:08 ` [Patch v3 3/4] RDMA/mana_ib : Create adapter and Add error eq sharmaajay
2023-07-28 3:02 ` [EXTERNAL] " Ajay Sharma
2023-07-28 21:56 ` Long Li
2023-07-26 20:08 ` [Patch v3 4/4] RDMA/mana_ib : Query adapter capabilities sharmaajay
2023-07-28 3:02 ` [EXTERNAL] " Ajay Sharma
2023-07-28 22:52 ` Long Li
2023-07-28 3:01 ` [EXTERNAL] [Patch v3 0/4] RDMA/mana_ib Read Capabilities Ajay Sharma
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=1690402104-29518-1-git-send-email-sharmaajay@linuxonhyperv.com \
--to=sharmaajay@linuxonhyperv.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharmaajay@microsoft.com \
--cc=wei.liu@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).