From: Saeed Mahameed <saeed@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [pull request][net-next V2 00/15] mlx5 updates 2023-03-20
Date: Fri, 24 Mar 2023 16:13:26 -0700 [thread overview]
Message-ID: <20230324231341.29808-1-saeed@kernel.org> (raw)
From: Saeed Mahameed <saeedm@nvidia.com>
v1->v2:
1) Improved commit messages
2) Added reviewed by Jacob Keller
3) handled Checkpatch errors
4) CC Thomas
5) Proper errno return values
6) Avoid "glue" leakage.
7) Removed unnecessary Fixes tag.
This series from Eli, adds the support for dynamic msix and irq vector
allocation in mlx5, required for mlx5 vdpa posted interrupt feature [1].
For more information please see tag log below.
Please pull and let me know if there is any problem.
The following changes since commit e8d018dd0257f744ca50a729e3d042cf2ec9da65:
Linux 6.3-rc3 (2023-03-19 13:27:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-updates-2023-03-20
for you to fetch changes up to 2e21ab28e230fd8333ac0586901431132cc308d7:
vdpa/mlx5: Support interrupt bypassing (2023-03-24 16:08:40 -0700)
----------------------------------------------------------------
mlx5-updates-2023-03-20
mlx5 dynamic msix
This patch series adds support for dynamic msix vectors allocation in mlx5.
Eli Cohen Says:
================
The following series of patches modifies mlx5_core to work with the
dynamic MSIX API. Currently, mlx5_core allocates all the interrupt
vectors it needs and distributes them amongst the consumers. With the
introduction of dynamic MSIX support, which allows for allocation of
interrupts more than once, we now allocate vectors as we need them.
This allows other drivers running on top of mlx5_core to allocate
interrupt vectors for their own use. An example for this is mlx5_vdpa,
which uses these vectors to propagate interrupts directly from the
hardware to the vCPU [1].
As a preparation for using this series, a use after free issue is fixed
in lib/cpu_rmap.c and the allocator for rmap entries has been modified.
A complementary API for irq_cpu_rmap_add() has also been introduced.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git/patch/?id=0f2bf1fcae96a83b8c5581854713c9fc3407556e
================
----------------------------------------------------------------
Eli Cohen (15):
lib: cpu_rmap: Avoid use after free on rmap->obj array entries
lib: cpu_rmap: Use allocator for rmap entries
lib: cpu_rmap: Add irq_cpu_rmap_remove to complement irq_cpu_rmap_add
net/mlx5e: Coding style fix, add empty line
net/mlx5: Fix wrong comment
net/mlx5: Modify struct mlx5_irq to use struct msi_map
net/mlx5: Use newer affinity descriptor
net/mlx5: Improve naming of pci function vectors
net/mlx5: Refactor completion irq request/release code
net/mlx5: Use dynamic msix vectors allocation
net/mlx5: Move devlink registration before mlx5_load
net/mlx5: Refactor calculation of required completion vectors
net/mlx5: Use one completion vector if eth is disabled
net/mlx5: Provide external API for allocating vectors
vdpa/mlx5: Support interrupt bypassing
drivers/net/ethernet/mellanox/mlx5/core/dev.c | 14 +-
drivers/net/ethernet/mellanox/mlx5/core/devlink.h | 11 +
drivers/net/ethernet/mellanox/mlx5/core/eq.c | 220 ++++++++++--------
.../net/ethernet/mellanox/mlx5/core/irq_affinity.c | 42 ++--
drivers/net/ethernet/mellanox/mlx5/core/main.c | 17 +-
drivers/net/ethernet/mellanox/mlx5/core/mlx5_irq.h | 10 +-
drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c | 248 +++++++++++++++------
drivers/net/ethernet/mellanox/mlx5/core/pci_irq.h | 4 +-
drivers/vdpa/mlx5/net/mlx5_vnet.c | 139 +++++++++++-
drivers/vdpa/mlx5/net/mlx5_vnet.h | 14 ++
include/linux/cpu_rmap.h | 4 +-
include/linux/mlx5/driver.h | 6 +
lib/cpu_rmap.c | 57 ++++-
13 files changed, 542 insertions(+), 244 deletions(-)
next reply other threads:[~2023-03-24 23:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 23:13 Saeed Mahameed [this message]
2023-03-24 23:13 ` [net-next V2 01/15] lib: cpu_rmap: Avoid use after free on rmap->obj array entries Saeed Mahameed
2023-03-29 7:00 ` patchwork-bot+netdevbpf
2023-03-24 23:13 ` [net-next V2 02/15] lib: cpu_rmap: Use allocator for rmap entries Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 03/15] lib: cpu_rmap: Add irq_cpu_rmap_remove to complement irq_cpu_rmap_add Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 04/15] net/mlx5e: Coding style fix, add empty line Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 05/15] net/mlx5: Fix wrong comment Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 06/15] net/mlx5: Modify struct mlx5_irq to use struct msi_map Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 07/15] net/mlx5: Use newer affinity descriptor Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 08/15] net/mlx5: Improve naming of pci function vectors Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 09/15] net/mlx5: Refactor completion irq request/release code Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 10/15] net/mlx5: Use dynamic msix vectors allocation Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 11/15] net/mlx5: Move devlink registration before mlx5_load Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 12/15] net/mlx5: Refactor calculation of required completion vectors Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 13/15] net/mlx5: Use one completion vector if eth is disabled Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 14/15] net/mlx5: Provide external API for allocating vectors Saeed Mahameed
2023-03-24 23:13 ` [net-next V2 15/15] vdpa/mlx5: Support interrupt bypassing Saeed Mahameed
2023-03-25 1:26 ` [pull request][net-next V2 00/15] mlx5 updates 2023-03-20 Saeed Mahameed
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=20230324231341.29808-1-saeed@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=tglx@linutronix.de \
/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).