DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Minggang Li(Gavin)" <gavinl@nvidia.com>
To: <matan@nvidia.com>, <viacheslavo@nvidia.com>, <orika@nvidia.com>,
	<thomas@monjalon.net>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH V1 0/7] port probe time optimization
Date: Mon, 23 Dec 2024 12:10:54 +0200	[thread overview]
Message-ID: <20241223101101.677449-1-gavinl@nvidia.com> (raw)

This patch series introduced a feature that the time to probe a VF/SF will
be reduced greatly in large scale, eg hundreds of VF/SFs. This feature is
controlled through the "probe_opt_en" device argument. Setting it to a
non-zero value indicates the application will enable this functionality
when probing a device. This feature relies on a feature of RDMA driver to
be release in incoming upstream kernel 6.12 or the equivalent in
OFED 24.10, ie. RDMA monitor. For further information on the devargs
limitation, see "doc/guides/nics/mlx5.rst".

Minggang Li(Gavin) (5):
  mailmap: update user name
  common/mlx5: fix Netlink socket leak
  common/mlx5: add RDMA monitor event awareness
  mlx5: use RDMA Netlink to update port information
  mlx5: add backward compatibility for RDMA monitor

Rongwei Liu (2):
  net/mlx5: optimize device probing
  net/mlx5: add new devargs to control probe optimization

 .mailmap                                     |   2 +-
 doc/guides/nics/mlx5.rst                     |  13 +
 doc/guides/rel_notes/release_24_11.rst       |  14 +
 drivers/common/mlx5/linux/meson.build        |  10 +
 drivers/common/mlx5/linux/mlx5_common_os.h   |   6 +
 drivers/common/mlx5/linux/mlx5_nl.c          | 262 ++++++++++++++++---
 drivers/common/mlx5/linux/mlx5_nl.h          |  36 ++-
 drivers/common/mlx5/mlx5_common.c            |  20 ++
 drivers/common/mlx5/mlx5_common.h            |  15 ++
 drivers/common/mlx5/version.map              |   3 +
 drivers/common/mlx5/windows/mlx5_common_os.h |   5 +
 drivers/net/mlx5/linux/mlx5_ethdev_os.c      | 136 ++++++++++
 drivers/net/mlx5/linux/mlx5_os.c             | 144 ++++++++--
 drivers/net/mlx5/linux/mlx5_os.h             |   6 -
 drivers/net/mlx5/mlx5.h                      |   3 +
 drivers/net/mlx5/windows/mlx5_os.h           |   5 -
 16 files changed, 605 insertions(+), 75 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-12-23 10:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-23 10:10 Minggang Li(Gavin) [this message]
2024-12-23 10:10 ` [PATCH 1/7] mailmap: update user name Minggang Li(Gavin)
2024-12-23 10:10 ` [PATCH 2/7] net/mlx5: optimize device probing Minggang Li(Gavin)
2024-12-23 10:10 ` [PATCH 3/7] net/mlx5: add new devargs to control probe optimization Minggang Li(Gavin)
2024-12-23 10:10 ` [PATCH 4/7] common/mlx5: fix Netlink socket leak Minggang Li(Gavin)
2024-12-23 10:10 ` [PATCH 5/7] common/mlx5: add RDMA monitor event awareness Minggang Li(Gavin)
2024-12-23 10:11 ` [PATCH 6/7] mlx5: use RDMA Netlink to update port information Minggang Li(Gavin)
2024-12-23 10:11 ` [PATCH 7/7] mlx5: add backward compatibility for RDMA monitor Minggang Li(Gavin)
  -- strict thread matches above, loose matches on Subject: below --
2024-10-16  8:38 [PATCH V1 0/7] port probe time optimization Minggang Li(Gavin)

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=20241223101101.677449-1-gavinl@nvidia.com \
    --to=gavinl@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@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).