public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Tariq Toukan <tariqt@nvidia.com>
To: Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>,
	Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
	<netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Gal Pressman <gal@nvidia.com>,
	Moshe Shemesh <moshe@nvidia.com>,
	Carolina Jubran <cjubran@nvidia.com>,
	Cosmin Ratiu <cratiu@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: [PATCH net-next 0/6] net/mlx5: Move notifiers outside the devlink lock
Date: Sun, 16 Nov 2025 22:45:34 +0200	[thread overview]
Message-ID: <1763325940-1231508-1-git-send-email-tariqt@nvidia.com> (raw)

Hi,

This series by Cosmin moves blocking notifier registration in the mlx5
driver outside the devlink lock during probe.

This is mostly a no-op refactoring that consists of multiple pieces.
It is necessary because upcoming code will introduce a potential locking
cycle between the devlink lock and the blocking notifier head mutexes,
so these notifiers must move out of the devlink-locked critical section.

Regards,
Tariq


Cosmin Ratiu (6):
  net/mlx5: Initialize events outside devlink lock
  net/mlx5: Move the esw mode notifier chain outside the devlink lock
  net/mlx5: Move the vhca event notifier outside of the devlink lock
  net/mlx5: Move the SF HW table notifier outside the devlink lock
  net/mlx5: Move the SF table notifiers outside the devlink lock
  net/mlx5: Move SF dev table notifier registration outside the PF
    devlink lock

 .../net/ethernet/mellanox/mlx5/core/eswitch.c | 13 +--
 .../net/ethernet/mellanox/mlx5/core/eswitch.h |  7 +-
 .../net/ethernet/mellanox/mlx5/core/main.c    | 70 +++++++++++----
 .../ethernet/mellanox/mlx5/core/sf/dev/dev.c  | 48 ++++++----
 .../ethernet/mellanox/mlx5/core/sf/dev/dev.h  | 11 +++
 .../ethernet/mellanox/mlx5/core/sf/devlink.c  | 90 ++++++++++++-------
 .../ethernet/mellanox/mlx5/core/sf/hw_table.c | 61 ++++++++-----
 .../net/ethernet/mellanox/mlx5/core/sf/sf.h   | 20 ++++-
 .../mellanox/mlx5/core/sf/vhca_event.c        | 69 ++++++--------
 .../mellanox/mlx5/core/sf/vhca_event.h        |  5 ++
 include/linux/mlx5/driver.h                   | 10 ++-
 11 files changed, 253 insertions(+), 151 deletions(-)


base-commit: c9dfb92de0738eb7fe6a591ad1642333793e8b6e
-- 
2.31.1


             reply	other threads:[~2025-11-16 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 20:45 Tariq Toukan [this message]
2025-11-16 20:45 ` [PATCH net-next 1/6] net/mlx5: Initialize events outside devlink lock Tariq Toukan
2025-11-16 20:45 ` [PATCH net-next 2/6] net/mlx5: Move the esw mode notifier chain outside the " Tariq Toukan
2025-11-16 20:45 ` [PATCH net-next 3/6] net/mlx5: Move the vhca event notifier outside of " Tariq Toukan
2025-11-16 20:45 ` [PATCH net-next 4/6] net/mlx5: Move the SF HW table notifier outside " Tariq Toukan
2025-11-16 20:45 ` [PATCH net-next 5/6] net/mlx5: Move the SF table notifiers " Tariq Toukan
2025-11-16 20:45 ` [PATCH net-next 6/6] net/mlx5: Move SF dev table notifier registration outside the PF " Tariq Toukan
2025-11-20  4:40 ` [PATCH net-next 0/6] net/mlx5: Move notifiers outside the " patchwork-bot+netdevbpf

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=1763325940-1231508-1-git-send-email-tariqt@nvidia.com \
    --to=tariqt@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=cjubran@nvidia.com \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=moshe@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox