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>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>
Subject: [pull request][net-next V5 00/15] mlx5 socket direct (Multi-PF)
Date: Tue, 5 Mar 2024 19:02:43 -0800 [thread overview]
Message-ID: <20240306030258.16874-1-saeed@kernel.org> (raw)
From: Saeed Mahameed <saeedm@nvidia.com>
Support Socket-Direct multi-dev netdev.
V5:
- Address documentation comments from Przemek Kitszel.
V4:
- Improve documentation for better user observability and understanding
of the feature, in terms of queues and their expected NUMA/CPU/IRQ
affinity.
V3:
- Fix documentation per Jakubs feedback.
- Fix typos
- Link new documentation in the networking index.rst
V2:
- Add documentation in a new patch.
- Add debugfs in a new patch.
- Add mlx5_ifc bit for MPIR cap check and use it before query.
For more information please see tag log below.
Please pull and let me know if there is any problem.
Thanks,
Saeed.
The following changes since commit 4166204d7ec26aee3d1f26847e88e4e41841fbe3:
net: tap: Remove generic .ndo_get_stats64 (2024-03-05 18:32:33 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-socket-direct-v3
for you to fetch changes up to 23d8025212973dc6a42a341e550a8907bf7ede4a:
Documentation: networking: Add description for multi-pf netdev (2024-03-05 18:59:33 -0800)
----------------------------------------------------------------
Support Multi-PF netdev (Socket Direct)
This series adds support for combining multiple devices (PFs) of the
same port under one netdev instance. Passing traffic through different
devices belonging to different NUMA sockets saves cross-numa traffic and
allows apps running on the same netdev from different numas to still
feel a sense of proximity to the device and achieve improved
performance.
We achieve this by grouping PFs together, and creating the netdev only
once all group members are probed. Symmetrically, we destroy the netdev
once any of the PFs is removed.
The channels are distributed between all devices, a proper configuration
would utilize the correct close numa when working on a certain app/cpu.
We pick one device to be a primary (leader), and it fills a special
role. The other devices (secondaries) are disconnected from the network
in the chip level (set to silent mode). All RX/TX traffic is steered
through the primary to/from the secondaries.
Currently, we limit the support to PFs only, and up to two devices
(sockets).
V5:
- Address documentation comments from Przemek Kitszel.
V4:
- Improve documentation for better user observability and understanding
of the feature, in terms of queues and their expected NUMA/CPU/IRQ
affinity.
V3:
- Fix documentation per Jakubs feedback.
- Fix typos
- Link new documentation in the networking index.rst
V2:
- Add documentation in a new patch.
- Add debugfs in a new patch.
- Add mlx5_ifc bit for MPIR cap check and use it before query.
----------------------------------------------------------------
Tariq Toukan (15):
net/mlx5: Add MPIR bit in mcam_access_reg
net/mlx5: SD, Introduce SD lib
net/mlx5: SD, Implement basic query and instantiation
net/mlx5: SD, Implement devcom communication and primary election
net/mlx5: SD, Implement steering for primary and secondaries
net/mlx5: SD, Add informative prints in kernel log
net/mlx5: SD, Add debugfs
net/mlx5e: Create single netdev per SD group
net/mlx5e: Create EN core HW resources for all secondary devices
net/mlx5e: Let channels be SD-aware
net/mlx5e: Support cross-vhca RSS
net/mlx5e: Support per-mdev queue counter
net/mlx5e: Block TLS device offload on combined SD netdev
net/mlx5: Enable SD feature
Documentation: networking: Add description for multi-pf netdev
Documentation/networking/index.rst | 1 +
Documentation/networking/multi-pf-netdev.rst | 174 +++++++
drivers/net/ethernet/mellanox/mlx5/core/Makefile | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/en.h | 9 +-
.../net/ethernet/mellanox/mlx5/core/en/channels.c | 10 +-
.../net/ethernet/mellanox/mlx5/core/en/channels.h | 6 +-
.../ethernet/mellanox/mlx5/core/en/monitor_stats.c | 48 +-
.../net/ethernet/mellanox/mlx5/core/en/params.c | 9 +-
.../net/ethernet/mellanox/mlx5/core/en/params.h | 3 -
drivers/net/ethernet/mellanox/mlx5/core/en/ptp.c | 12 +-
drivers/net/ethernet/mellanox/mlx5/core/en/qos.c | 8 +-
.../ethernet/mellanox/mlx5/core/en/reporter_rx.c | 4 +-
.../ethernet/mellanox/mlx5/core/en/reporter_tx.c | 3 +-
drivers/net/ethernet/mellanox/mlx5/core/en/rqt.c | 123 ++++-
drivers/net/ethernet/mellanox/mlx5/core/en/rqt.h | 9 +-
drivers/net/ethernet/mellanox/mlx5/core/en/rss.c | 17 +-
drivers/net/ethernet/mellanox/mlx5/core/en/rss.h | 4 +-
.../net/ethernet/mellanox/mlx5/core/en/rx_res.c | 62 ++-
.../net/ethernet/mellanox/mlx5/core/en/rx_res.h | 1 +
drivers/net/ethernet/mellanox/mlx5/core/en/trap.c | 11 +-
.../net/ethernet/mellanox/mlx5/core/en/xsk/pool.c | 6 +-
.../net/ethernet/mellanox/mlx5/core/en/xsk/setup.c | 8 +-
.../ethernet/mellanox/mlx5/core/en_accel/ktls.c | 2 +-
.../ethernet/mellanox/mlx5/core/en_accel/ktls.h | 4 +-
.../ethernet/mellanox/mlx5/core/en_accel/ktls_rx.c | 6 +-
drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 176 +++++--
drivers/net/ethernet/mellanox/mlx5/core/en_stats.c | 39 +-
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 4 +-
.../net/ethernet/mellanox/mlx5/core/lib/devcom.h | 1 +
drivers/net/ethernet/mellanox/mlx5/core/lib/mlx5.h | 12 +
drivers/net/ethernet/mellanox/mlx5/core/lib/sd.c | 524 +++++++++++++++++++++
drivers/net/ethernet/mellanox/mlx5/core/lib/sd.h | 38 ++
include/linux/mlx5/driver.h | 1 +
include/linux/mlx5/mlx5_ifc.h | 4 +-
34 files changed, 1168 insertions(+), 173 deletions(-)
create mode 100644 Documentation/networking/multi-pf-netdev.rst
create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/lib/sd.c
create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/lib/sd.h
next reply other threads:[~2024-03-06 3:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 3:02 Saeed Mahameed [this message]
2024-03-06 3:02 ` [net-next V5 01/15] net/mlx5: Add MPIR bit in mcam_access_reg Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 02/15] net/mlx5: SD, Introduce SD lib Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 03/15] net/mlx5: SD, Implement basic query and instantiation Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 04/15] net/mlx5: SD, Implement devcom communication and primary election Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 05/15] net/mlx5: SD, Implement steering for primary and secondaries Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 06/15] net/mlx5: SD, Add informative prints in kernel log Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 07/15] net/mlx5: SD, Add debugfs Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 08/15] net/mlx5e: Create single netdev per SD group Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 09/15] net/mlx5e: Create EN core HW resources for all secondary devices Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 10/15] net/mlx5e: Let channels be SD-aware Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 11/15] net/mlx5e: Support cross-vhca RSS Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 12/15] net/mlx5e: Support per-mdev queue counter Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 13/15] net/mlx5e: Block TLS device offload on combined SD netdev Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 14/15] net/mlx5: Enable SD feature Saeed Mahameed
2024-03-06 3:02 ` [net-next V5 15/15] Documentation: networking: Add description for multi-pf netdev Saeed Mahameed
2024-03-07 4:53 ` Jakub Kicinski
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=20240306030258.16874-1-saeed@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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).