From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Walter Heymans <walter.heymans@corigine.com>,
Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH v2 2/3] doc: update outdated information for the nfp PMD
Date: Mon, 20 Feb 2023 16:41:10 +0800 [thread overview]
Message-ID: <20230220084111.40531-3-chaoyong.he@corigine.com> (raw)
In-Reply-To: <20230220084111.40531-1-chaoyong.he@corigine.com>
From: Walter Heymans <walter.heymans@corigine.com>
Update nfp documentation with new information and remove outdated
information. The most significant changes that are updated include:
- Previously the NFP PMD did not support functionality to control VFs,
it now does.
- Previously the PF had to be bound to the kernel driver to create VFs,
then VFs were created and bound to 'vfio-pci'. Currently it is
possible to bind the PF to 'vfio-pci' and create VFs bound to
'vfio-pci'.
- The name of the Linux kernel driver changed for VFs. Previously the
'nfp_netvf' module was used, but now both PFs and VFs use the 'nfp'
module.
Signed-off-by: Walter Heymans <walter.heymans@corigine.com>
Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
---
doc/guides/nics/nfp.rst | 40 +++++++++++++++++++---------------------
1 file changed, 19 insertions(+), 21 deletions(-)
diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
index 36c447a17c..d133b6385c 100644
--- a/doc/guides/nics/nfp.rst
+++ b/doc/guides/nics/nfp.rst
@@ -63,13 +63,6 @@ Refer to the document
Using the PF
------------
-NFP PMD supports using the NFP PF as another DPDK port, but it does not
-have any functionality for controlling VFs. In fact, it is not possible to use
-the PMD with the VFs if the PF is being used by DPDK, that is, with the NFP PF
-bound to ``igb_uio`` or ``vfio-pci`` kernel drivers. Future DPDK versions will
-have a PMD able to work with the PF and VFs at the same time and with the PF
-implementing VF management along with other PF-only functionalities/offloads.
-
The PMD PF has extra work to do which will delay the DPDK app initialization
like uploading the firmware and configure the Link state properly when starting
or stopping a PF port. Since DPDK 18.05 the firmware upload happens when
@@ -153,20 +146,25 @@ System configuration
#. **Enable SR-IOV on the NFP device:** The current NFP PMD supports the PF and
the VFs on a NFP device. However, it is not possible to work with both at
- the same time because the VFs require the PF being bound to the NFP PF Linux
- netdev driver. Make sure you are working with a kernel with NFP PF support
- or get the drivers from the above Github repository and follow the
- instructions for building and installing it.
+ the same time when using the ``nfp`` Linux netdev kernel driver. If the PF
+ is bound to the ``nfp`` kernel module, and VFs are created, the VFs may be
+ bound to the ``vfio-pci`` kernel module. It is also possible to bind the PF
+ to the ``vfio-pci`` kernel module, and create VFs afterwards. This requires
+ loading the ``vfio-pci`` module with the following parameters:
+
+ .. code-block:: console
+
+ modprobe vfio-pci enable_sriov=1 disable_idle_d3=1
- VFs need to be enabled before they can be used with the PMD.
- Before enabling the VFs it is useful to obtain information about the
- current NFP PCI device detected by the system:
+ VFs need to be enabled before they can be used with the PMD. Before enabling
+ the VFs it is useful to obtain information about the current NFP PCI device
+ detected by the system. This can be done on Netronome SmartNICs using:
.. code-block:: console
- lspci -d19ee:
+ lspci -d 19ee:
- Now, for example, configure two virtual functions on a NFP-6xxx device
+ Now, for example, to configure two virtual functions on a NFP device
whose PCI system identity is "0000:03:00.0":
.. code-block:: console
@@ -177,12 +175,12 @@ System configuration
.. code-block:: console
- lspci -d19ee: -k
+ lspci -kd 19ee:
Two new PCI devices should appear in the output of the above command. The
-k option shows the device driver, if any, that the devices are bound to.
- Depending on the modules loaded at this point the new PCI devices may be
- bound to nfp_netvf driver.
+ Depending on the modules loaded, at this point the new PCI devices may be
+ bound to the ``nfp`` kernel driver or ``vfio-pci``.
Flow offload
@@ -209,8 +207,8 @@ vNIC service will keep polling packets from the firmware, and multiplex them
to the corresponding representor port.
In the Tx direction, the representor port will prepend the output port
-information into metadata for each packet, and then send it to firmware through
-PF vNIC.
+information into metadata for each packet, and then send it to the firmware
+through the PF vNIC.
The ctrl vNIC service handles various control messages, for example, the
creation and configuration of representor port, the pattern and action of flow
--
2.29.3
next prev parent reply other threads:[~2023-02-20 8:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 8:08 [PATCH] doc: update NFP documentation with Corigine information Chaoyong He
2023-02-15 13:37 ` Ferruh Yigit
2023-02-15 17:58 ` Niklas Söderlund
2023-02-20 8:41 ` [PATCH v2 0/3] update NFP documentation Chaoyong He
2023-02-20 8:41 ` [PATCH v2 1/3] doc: wrap nfp doc to 80 characters and improve grammar Chaoyong He
2023-02-20 8:41 ` Chaoyong He [this message]
2023-02-20 12:25 ` [PATCH v2 2/3] doc: update outdated information for the nfp PMD Ferruh Yigit
2023-02-21 9:04 ` Chaoyong He
2023-02-21 9:29 ` Ferruh Yigit
2023-02-21 10:11 ` Chaoyong He
2023-02-21 10:42 ` Ferruh Yigit
2023-02-20 8:41 ` [PATCH v2 3/3] doc: add Corigine information to nfp documentation Chaoyong He
2023-02-22 1:23 ` [PATCH v2 0/3] update NFP documentation Ferruh Yigit
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=20230220084111.40531-3-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=walter.heymans@corigine.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).