DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jiawei Wang <jiaweiw@nvidia.com>
To: <bingz@nvidia.com>, <dsosnowski@nvidia.com>,
	<thomas@monjalon.net>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH] doc: update the doc for support multi-host lag probe
Date: Tue, 30 Sep 2025 15:02:47 +0300	[thread overview]
Message-ID: <20250930120247.24926-1-jiaweiw@nvidia.com> (raw)

On the ConnectX-7 Multi-Host Setup, the PF index is not continuous,
user need to query the PF index based on the return value of the
related sysfs entries:
    cat /sys/class/net/*/phys_port_name

Example output is 0 and 2 for PF1 and PF2, then use 0 and 2 of PF index::
   -a <Primary_PCI_BDF>,representor=pf[0,2]vf[0-2]

Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
---
 doc/guides/nics/mlx5.rst | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 20056f61d6..4aeb5b49da 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -744,6 +744,16 @@ for an additional list of options shared with other mlx5 drivers.
 
     <Primary_PCI_BDF>,representor=pf[0,1]vf[0-2]
 
+  To probe VF port representors 0 through 2 on both PFs of bonding device on
+  ConnectX-7 Multi-Host Setup, the PF index is not continuous, user need to
+  query the PF index based on the return value of the related sysfs entries::
+
+    cat /sys/class/net/*/phys_port_name
+
+  Example output is 0 and 2 for PF1 and PF2, then use [0,2] for PF index::
+
+    <Primary_PCI_BDF>,representor=pf[0,2]vf[0-2]
+
 - ``repr_matching_en`` parameter [int]
 
   - 0. If representor matching is disabled, then there will be no implicit
-- 
2.18.1


                 reply	other threads:[~2025-09-30 12:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250930120247.24926-1-jiaweiw@nvidia.com \
    --to=jiaweiw@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@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).