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>,
Dragos Tatulea <dtatulea@nvidia.com>,
Daniel Jurgens <danielj@nvidia.com>, William Tu <witu@nvidia.com>
Subject: [PATCH net-next 0/2] net/mlx5: Support disabling host PFs
Date: Wed, 13 Aug 2025 22:19:54 +0300 [thread overview]
Message-ID: <1755112796-467444-1-git-send-email-tariqt@nvidia.com> (raw)
Hi,
This small series by Daniel adds support for disabling host PFs.
If device is capable and configured, the driver won't access vports of
disabled host functions.
Regards,
Tariq
Daniel Jurgens (2):
net/mlx5: Query to see if host PF is disabled
net/mlx5: Support disabling host PFs
.../net/ethernet/mellanox/mlx5/core/eswitch.c | 85 ++++++++++++++-----
.../net/ethernet/mellanox/mlx5/core/eswitch.h | 8 ++
.../mellanox/mlx5/core/eswitch_offloads.c | 34 +++++---
3 files changed, 90 insertions(+), 37 deletions(-)
base-commit: fdbe93b7f0f86c943351ceab26c8fad548869f91
--
2.31.1
next reply other threads:[~2025-08-13 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 19:19 Tariq Toukan [this message]
2025-08-13 19:19 ` [PATCH net-next 1/2] net/mlx5: Query to see if host PF is disabled Tariq Toukan
2025-08-13 19:19 ` [PATCH net-next 2/2] net/mlx5: Support disabling host PFs Tariq Toukan
2025-08-15 19:50 ` [PATCH net-next 0/2] " 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=1755112796-467444-1-git-send-email-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=witu@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;
as well as URLs for NNTP newsgroup(s).