From: Konstantin Taranov <kotaranov@linux.microsoft.com>
To: kotaranov@microsoft.com, pabeni@redhat.com,
haiyangz@microsoft.com, kys@microsoft.com, edumazet@google.com,
kuba@kernel.org, davem@davemloft.net, decui@microsoft.com,
wei.liu@kernel.org, longli@microsoft.com, jgg@ziepe.ca,
leon@kernel.org
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH rdma-next 0/4] RDMA/mana_ib: allow separate mana_ib for each mana client
Date: Mon, 14 Apr 2025 11:28:45 -0700 [thread overview]
Message-ID: <1744655329-13601-1-git-send-email-kotaranov@linux.microsoft.com> (raw)
From: Konstantin Taranov <kotaranov@microsoft.com>
Microsoft mana adapter has 2 devices in the HW: mana ethernet device and RNIC device.
Both devices can implement RDMA drivers and, so far, they have been sharing
one ib device context. However, they are different devices with different
capabilities in the HW and have different lifetime model.
This series allows us to model the aforementioned two devices as separate ib devices.
The mana_ib will continue supporting two devices but as individual ib devices.
It enables the driver to dynamically destroy and create the auxiliary device over
RNIC, when the HW reboots the RNIC module. Without this separation, the reboot
would cause destruction of the ib device serving DPDK clients from the uninterrupted
ethernet HW module.
This patch series depend on the patch "RDMA/mana_ib: Add support of 4M, 1G, and 2G pages".
Konstantin Taranov (3):
net: mana: Probe rdma device in mana driver
RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic
RDMA/mana_ib: unify mana_ib functions to support any gdma device
Shiraz Saleem (1):
net: mana: Add support for auxiliary device servicing events
drivers/infiniband/hw/mana/cq.c | 4 +-
drivers/infiniband/hw/mana/device.c | 174 +++++++++---------
drivers/infiniband/hw/mana/main.c | 77 ++++++--
drivers/infiniband/hw/mana/mana_ib.h | 6 +
drivers/infiniband/hw/mana/qp.c | 5 +-
.../net/ethernet/microsoft/mana/gdma_main.c | 27 ++-
.../net/ethernet/microsoft/mana/hw_channel.c | 19 ++
drivers/net/ethernet/microsoft/mana/mana_en.c | 99 +++++++++-
include/net/mana/gdma.h | 18 ++
include/net/mana/hw_channel.h | 9 +
include/net/mana/mana.h | 3 +
11 files changed, 320 insertions(+), 121 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-14 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 18:28 Konstantin Taranov [this message]
2025-04-14 18:28 ` [PATCH rdma-next 1/4] net: mana: Probe rdma device in mana driver Konstantin Taranov
2025-04-14 18:28 ` [PATCH rdma-next 2/4] RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic Konstantin Taranov
2025-04-14 18:28 ` [PATCH rdma-next 3/4] RDMA/mana_ib: unify mana_ib functions to support any gdma device Konstantin Taranov
2025-04-14 18:28 ` [PATCH rdma-next 4/4] net: mana: Add support for auxiliary device servicing events Konstantin Taranov
2025-04-20 10:53 ` Leon Romanovsky
2025-04-24 2:33 ` Shiraz Saleem
2025-04-24 10:49 ` Leon Romanovsky
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=1744655329-13601-1-git-send-email-kotaranov@linux.microsoft.com \
--to=kotaranov@linux.microsoft.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).