From: Michael Guralnik <michaelgur@nvidia.com>
To: <jgg@nvidia.com>
Cc: <linux-rdma@vger.kernel.org>, <leonro@nvidia.com>,
<mbloch@nvidia.com>, <cmeiohas@nvidia.com>, <msanalla@nvidia.com>,
Michael Guralnik <michaelgur@nvidia.com>
Subject: [PATCH rdma-next 0/7] Support RDMA events monitoring through
Date: Wed, 21 Aug 2024 08:10:10 +0300 [thread overview]
Message-ID: <20240821051017.7730-1-michaelgur@nvidia.com> (raw)
This series consists of multiple parts that collectively offer a method
to monitor RDMA events from userspace.
Using netlink, users will be able to monitor their IB device events and
changes such as device register, device unregister and netdev
attachment.
The first 2 patches contain fixes in mlx5 lag code that are required for
accurate event reporting in case of a lag bond.
Patch #3 initializes phys_port_cnt early in device probe to allow the
IB-to-netdev mapping API to work properly.
Patches #4,#5 modify and export IB-to-netdev mapping API, making it accessible
to all vendors who wish to rely on it for associating their IB device with
a netdevice.
Patches #6,#7 add the netlink support for reporting IB device events to
userspace.
Chiara Meiohas (4):
RDMA/mlx5: Initialize phys_port_cnt earlier in RDMA device creation
RDMA/mlx5: Use IB set_netdev and get_netdev functions
RDMA/nldev: Add support for RDMA monitoring
RDMA/nldev: Expose whether RDMA monitoring is supported
Maher Sanalla (1):
RDMA/device: Clear netdev mapping in ib_device_get_netdev on
unregistration
Mark Bloch (2):
RDMA/mlx5: Check RoCE LAG status before getting netdev
RDMA/mlx5: Obtain upper net device only when needed
drivers/infiniband/core/device.c | 43 ++++
drivers/infiniband/core/netlink.c | 1 +
drivers/infiniband/core/nldev.c | 123 +++++++++++
drivers/infiniband/hw/mlx5/ib_rep.c | 22 +-
drivers/infiniband/hw/mlx5/main.c | 197 +++++++++++++-----
drivers/infiniband/hw/mlx5/mlx5_ib.h | 3 +-
.../net/ethernet/mellanox/mlx5/core/lag/lag.c | 76 +++----
include/linux/mlx5/device.h | 1 +
include/linux/mlx5/driver.h | 2 +-
include/rdma/ib_verbs.h | 2 +
include/rdma/rdma_netlink.h | 10 +
include/uapi/rdma/rdma_netlink.h | 16 ++
12 files changed, 391 insertions(+), 105 deletions(-)
--
2.17.2
next reply other threads:[~2024-08-21 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 5:10 Michael Guralnik [this message]
2024-08-21 5:10 ` [PATCH rdma-next 1/7] RDMA/mlx5: Check RoCE LAG status before getting netdev Michael Guralnik
2024-08-21 5:10 ` [PATCH rdma-next 2/7] RDMA/mlx5: Obtain upper net device only when needed Michael Guralnik
2024-08-21 5:10 ` [PATCH rdma-next 3/7] RDMA/mlx5: Initialize phys_port_cnt earlier in RDMA device creation Michael Guralnik
2024-08-21 5:10 ` [PATCH rdma-next 4/7] RDMA/device: Clear netdev mapping in ib_device_get_netdev on unregistration Michael Guralnik
2024-08-21 5:10 ` [PATCH rdma-next 5/7] RDMA/mlx5: Use IB set_netdev and get_netdev functions Michael Guralnik
2024-08-21 5:10 ` [PATCH rdma-next 6/7] RDMA/nldev: Add support for RDMA monitoring Michael Guralnik
2024-08-21 19:18 ` kernel test robot
2024-08-21 20:30 ` kernel test robot
2024-08-21 5:10 ` [PATCH rdma-next 7/7] RDMA/nldev: Expose whether RDMA monitoring is supported Michael Guralnik
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=20240821051017.7730-1-michaelgur@nvidia.com \
--to=michaelgur@nvidia.com \
--cc=cmeiohas@nvidia.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=msanalla@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.