[dpdk-dev,2/6] qede: add documentation

Message ID 1455982831-21682-3-git-send-email-harish.patil@qlogic.com (mailing list archive)
State Changes Requested, archived
Delegated to: Bruce Richardson
Headers

Commit Message

Harish Patil Feb. 20, 2016, 3:40 p.m. UTC
  Signed-off-by: Harish Patil <harish.patil@qlogic.com>
Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com>
Signed-off-by: Sony Chacko <sony.chacko@qlogic.com>
---
 doc/guides/nics/index.rst |   1 +
 doc/guides/nics/qede.rst  | 344 ++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 345 insertions(+)
 create mode 100644 doc/guides/nics/qede.rst
  

Comments

John McNamara Feb. 22, 2016, 4:52 p.m. UTC | #1
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Harish Patil
> Sent: Saturday, February 20, 2016 3:40 PM
> To: dev@dpdk.org
> Cc: Sony Chacko <sony.chacko@qlogic.com>
> Subject: [dpdk-dev] [PATCH 2/6] qede: add documentation
> 
> Signed-off-by: Harish Patil <harish.patil@qlogic.com>
> Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com>
> Signed-off-by: Sony Chacko <sony.chacko@qlogic.com>
> ---
>  doc/guides/nics/index.rst |   1 +
>  doc/guides/nics/qede.rst  | 344

Hi,

Thanks for the docs. The overall format and content seem good. A few
comments below.


> +#. Bind the QLogic 579xx adapters to ``igb_uio`` or ``vfio-pci`` loaded
> in the
> +   previous step::
> +
> +      ./tools/dpdk_nic_bind.py --bind igb_uio 0000:84:00.0 0000:84:00.1
> + 0000:84:00.2 0000:84:00.3

Fixed width lines should be constrained to 80 characters or else they will
go off the page in the PDF docs. The usual workaround is to use a command-
line continuation (or text wrap). For example:


     ./tools/dpdk_nic_bind.py --bind igb_uio \
                              0000:84:00.0 0000:84:00.1 \
                              0000:84:00.2 0000:84:00.3

Or similar. This also applies to the command-lines in other sections.
> +
> +#. Start ``testpmd`` with basic parameters:
> +
> +   .. code-block:: console
> +
> +      testpmd -c 0xf8000 -n 4 -- -i --nb-cores=4 --portmask=0xf
> + --rxd=4096 --txd=4096 --txfreet=4068 --rxq=2 --txq=2 --rss-ip
> + --rss-udp

Same comment about using continuations.


> +
> +      [...]
> +
> +    EAL: PCI device 0000:84:00.0 on NUMA socket 1
> +    EAL:   probe driver: 1077:1634 rte_qede_pmd

Align the text in this section to the same level of indentation.


> +    EAL:   Not managed by a supported kernel driver, skipped
> +    EAL: PCI device 0000:84:00.1 on NUMA socket 1
> +    EAL:   probe driver: 1077:1634 rte_qede_pmd
> +    EAL:   Not managed by a supported kernel driver, skipped
> +    EAL: PCI device 0000:88:00.0 on NUMA socket 1
> +    EAL:   probe driver: 1077:1656 rte_qede_pmd
> +    EAL:   PCI memory mapped at 0x7f738b200000
> +    EAL:   PCI memory mapped at 0x7f738b280000
> +    EAL:   PCI memory mapped at 0x7f738b300000
> +    [QEDE PMD: (88:00.0:dpdk-port-0)]qed_load_firmware_data: Loading the
> firmware file /lib/firmware/qed/qed_init_values_zipped.bin...

Again, try wrap the code/console section at 80 chars in some way that still
maintains the meaning. Maybe something like the following (with a note to
say that the text has been wrapped for clarity):

    [QEDE PMD: (88:00.0:dpdk-port-0)]qed_load_firmware_data:
               Loading the firmware file
               /lib/firmware/qed/qed_init_values_zipped.bin...
    [QEDE PMD: (88:00.0:dpdk-port-0)]
               qede_print_adapter_info:Chip details - BB1
    [QEDE PMD: (88:00.0:dpdk-port-0)]
               qede_print_adapter_info:Driver version:QEDE PMD 8.7.9.0_1.0.0
    [QEDE PMD: (88:00.0:dpdk-port-0)]
               qede_print_adapter_info:Firmware version:8.7.7.0


You can test the PDF output as follows:

    make -j doc-guides-pdf
    pdf_veiwer build/doc/pdf/guides/nics.pdf

John
  
John McNamara Feb. 22, 2016, 5:38 p.m. UTC | #2
> +
> +   Assign MAC address to the VF using iproute2 utility. The syntax is:
> +   ip link set <PF iface> vf <VF id> mac <macaddr>

Also, make this a code/console section by adding :: to the previous line
and indenting 3-4 spaces.
  
Harish Patil Feb. 24, 2016, 7:17 a.m. UTC | #3
>>

>>-----Original Message-----

>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Harish Patil

>> Sent: Saturday, February 20, 2016 3:40 PM

>> To: dev@dpdk.org

>> Cc: Sony Chacko <sony.chacko@qlogic.com>

>> Subject: [dpdk-dev] [PATCH 2/6] qede: add documentation

>> 

>> Signed-off-by: Harish Patil <harish.patil@qlogic.com>

>> Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com>

>> Signed-off-by: Sony Chacko <sony.chacko@qlogic.com>

>> ---

>>  doc/guides/nics/index.rst |   1 +

>>  doc/guides/nics/qede.rst  | 344

>

>Hi,

>

>Thanks for the docs. The overall format and content seem good. A few

>comments below.

>

>

>> +#. Bind the QLogic 579xx adapters to ``igb_uio`` or ``vfio-pci`` loaded

>> in the

>> +   previous step::

>> +

>> +      ./tools/dpdk_nic_bind.py --bind igb_uio 0000:84:00.0 0000:84:00.1

>> + 0000:84:00.2 0000:84:00.3

>

>Fixed width lines should be constrained to 80 characters or else they will

>go off the page in the PDF docs. The usual workaround is to use a command-

>line continuation (or text wrap). For example:

>

>

>     ./tools/dpdk_nic_bind.py --bind igb_uio \

>                              0000:84:00.0 0000:84:00.1 \

>                              0000:84:00.2 0000:84:00.3

>

>Or similar. This also applies to the command-lines in other sections.

>> +

>> +#. Start ``testpmd`` with basic parameters:

>> +

>> +   .. code-block:: console

>> +

>> +      testpmd -c 0xf8000 -n 4 -- -i --nb-cores=4 --portmask=0xf

>> + --rxd=4096 --txd=4096 --txfreet=4068 --rxq=2 --txq=2 --rss-ip

>> + --rss-udp

>

>Same comment about using continuations.

>

>

>> +

>> +      [...]

>> +

>> +    EAL: PCI device 0000:84:00.0 on NUMA socket 1

>> +    EAL:   probe driver: 1077:1634 rte_qede_pmd

>

>Align the text in this section to the same level of indentation.

>

>

>> +    EAL:   Not managed by a supported kernel driver, skipped

>> +    EAL: PCI device 0000:84:00.1 on NUMA socket 1

>> +    EAL:   probe driver: 1077:1634 rte_qede_pmd

>> +    EAL:   Not managed by a supported kernel driver, skipped

>> +    EAL: PCI device 0000:88:00.0 on NUMA socket 1

>> +    EAL:   probe driver: 1077:1656 rte_qede_pmd

>> +    EAL:   PCI memory mapped at 0x7f738b200000

>> +    EAL:   PCI memory mapped at 0x7f738b280000

>> +    EAL:   PCI memory mapped at 0x7f738b300000

>> +    [QEDE PMD: (88:00.0:dpdk-port-0)]qed_load_firmware_data: Loading

>>the

>> firmware file /lib/firmware/qed/qed_init_values_zipped.bin...

>

>Again, try wrap the code/console section at 80 chars in some way that

>still

>maintains the meaning. Maybe something like the following (with a note to

>say that the text has been wrapped for clarity):

>

>    [QEDE PMD: (88:00.0:dpdk-port-0)]qed_load_firmware_data:

>               Loading the firmware file

>               /lib/firmware/qed/qed_init_values_zipped.bin...

>    [QEDE PMD: (88:00.0:dpdk-port-0)]

>               qede_print_adapter_info:Chip details - BB1

>    [QEDE PMD: (88:00.0:dpdk-port-0)]

>               qede_print_adapter_info:Driver version:QEDE PMD

>8.7.9.0_1.0.0

>    [QEDE PMD: (88:00.0:dpdk-port-0)]

>               qede_print_adapter_info:Firmware version:8.7.7.0

>

>

>You can test the PDF output as follows:

>

>    make -j doc-guides-pdf

>    pdf_veiwer build/doc/pdf/guides/nics.pdf

>

>John

>


These are the actual output from the console that was pasted, that’s why
they are more than 80 chars.
Sure, will take care of that as you mentioned.


Thanks,
Harish
  
John McNamara Feb. 24, 2016, 9:26 a.m. UTC | #4
> -----Original Message-----

> From: Harish Patil [mailto:harish.patil@qlogic.com]

> Sent: Wednesday, February 24, 2016 7:18 AM

> To: Mcnamara, John <john.mcnamara@intel.com>; dev@dpdk.org

> Subject: Re: [dpdk-dev] [PATCH 2/6] qede: add documentation

> 

> >>

> >

> >Again, try wrap the code/console section at 80 chars in some way that

> >still maintains the meaning. Maybe something like the following (with a

> >note to say that the text has been wrapped for clarity):

> >

> > ...

> 

> These are the actual output from the console that was pasted, that’s why

> they are more than 80 chars.

> Sure, will take care of that as you mentioned.


Hi,

I understand that the text is actual output but if you generate the pdf
documentation you will see that the fixed width text goes off the page.
So some sort of compromise is required and wrapping the text is what
is usually done in the DPDK docs.

Since it may be confusing to the end user if they see different output
in the docs and on the console it is probably worth adding a line in the
preceding paragraph to say something like "(text wrapped for clarity)".

John.
--
  

Patch

diff --git a/doc/guides/nics/index.rst b/doc/guides/nics/index.rst
index 8618114..f092f75 100644
--- a/doc/guides/nics/index.rst
+++ b/doc/guides/nics/index.rst
@@ -50,6 +50,7 @@  Network Interface Controller Drivers
     virtio
     vmxnet3
     pcap_ring
+    qede
 
 **Figures**
 
diff --git a/doc/guides/nics/qede.rst b/doc/guides/nics/qede.rst
new file mode 100644
index 0000000..de4fecd
--- /dev/null
+++ b/doc/guides/nics/qede.rst
@@ -0,0 +1,344 @@ 
+..  BSD LICENSE
+    Copyright (c) 2016 QLogic Corporation
+    All rights reserved.
+
+    Redistribution and use in source and binary forms, with or without
+    modification, are permitted provided that the following conditions
+    are met:
+
+    * Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in
+    the documentation and/or other materials provided with the
+    distribution.
+    * Neither the name of QLogic Corporation nor the names of its
+    contributors may be used to endorse or promote products derived
+    from this software without specific prior written permission.
+
+    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+QEDE Poll Mode Driver
+======================
+
+The QEDE poll mode driver library (**librte_pmd_qede**) implements support
+for **QLogic FastLinQ QL4xxxx 25G/40G CNA** family of adapters as well
+as their virtual functions (VF) in SR-IOV context. It is supported on
+several standard Linux distros like RHEL7.x and SLES12.x OS.
+It is compile-tested under FreeBSD OS.
+
+More information can be found at `QLogic Corporation's Official Website
+<http://www.qlogic.com>`_.
+
+Supported Features
+------------------
+
+- Unicast/multicast/VLAN filtering
+- Promiscuous mode
+- Allmulti mode
+- Port hardware statistics
+- Jumbo frames (using single buffer)
+- VLAN tag insertion/removal
+- Stateless checksum offloads (IPv4/TCP/UDP)
+- Multiple Rx/Tx queues (queue-pairs)
+- RSS (with default table/key)
+- TSS
+- Multiple MAC address
+- Default pause flow control
+- SR-IOV VF
+
+Non-supported Features
+----------------------
+
+- Scatter-Gather Rx/Tx frames
+- User configurable RETA table/key
+- Unequal number of Rx/Tx queues
+- MTU change (dynamic)
+- SR-IOV PF
+- Tunneling offloads
+
+Supported QLogic NICs
+---------------------
+
+- QLogic FastLinQ QL4xxxx 25G/40G CNAs
+
+Prerequisites
+-------------
+
+- Requires storm firmware version **8.7.x.** and management
+  firmware version **8.7.x and higher**. Storm firmware may be available
+  under /usr/lib/firmware/qed/ in certain newer Linux
+  distributions (e.g. qed_init_values_zipped-8.7.8.0.bin).
+
+- If the required firmware files are not available then visit
+  `QLogic Driver Download Center <http://driverdownloads.qlogic.com>`
+
+- This driver relies on external zlib library (-lz) for uncompressing
+  the firmware file.
+
+Config File Options
+~~~~~~~~~~~~~~~~~~~
+
+The following options can be modified in the ``.config`` file. Please note that
+enabling debugging options may affect system performance.
+
+- ``CONFIG_RTE_LIBRTE_QEDE_PMD`` (default **y**)
+
+  Toggle compilation of QEDE PMD driver.
+
+- ``CONFIG_RTE_LIBRTE_QEDE_DEBUG_INFO`` (default **n**)
+
+  Toggle display of generic debugging messages.
+
+- ``CONFIG_RTE_LIBRTE_QEDE_DEBUG_ECORE`` (default **n**)
+
+  Toggle display of ecore related messages.
+
+- ``CONFIG_RTE_LIBRTE_QEDE_DEBUG_TX`` (default **n**)
+
+  Toggle display of transmit fast path run-time messages.
+
+- ``CONFIG_RTE_LIBRTE_QEDE_DEBUG_RX`` (default **n**)
+
+  Toggle display of receive fast path run-time messages.
+
+- ``CONFIG_RTE_LIBRTE_QEDE_RX_COAL_US`` (default **24**)
+
+  Change Rx interrupt coalescing timer (in us).
+
+- ``CONFIG_RTE_LIBRTE_QEDE_TX_COAL_US`` (default **48**)
+
+  Change Tx interrupt coalescing timer (in us).
+
+- ``CONFIG_RTE_LIBRTE_QEDE_TX_SWITCHING`` (default **y**)
+
+  Toggle Tx switching
+
+- ``CONFIG_RTE_LIBRTE_QEDE_FW`` (default **n**)
+
+  Path of firmware file (overrides default location)
+
+Driver Compilation
+~~~~~~~~~~~~~~~~~~
+
+To compile QEDE PMD for Linux x86_64 gcc target, run the following "make"
+command::
+
+   cd <DPDK-source-directory>
+   make config T=x86_64-native-linuxapp-gcc install
+
+To compile QEDE PMD for Linux x86_64 clang target, run the following "make"
+command::
+
+   cd <DPDK-source-directory>
+   make config T=x86_64-native-linuxapp-clang install
+
+To compile QEDE PMD for FreeBSD x86_64 clang target, run the following "gmake"
+command::
+
+   cd <DPDK-source-directory>
+   gmake config T=x86_64-native-bsdapp-clang install
+
+To compile QEDE PMD for FreeBSD x86_64 gcc target, run the following "gmake"
+command::
+
+   cd <DPDK-source-directory>
+   gmake config T=x86_64-native-bsdapp-gcc install -Wl,-rpath=/usr/local/lib/gcc48 CC=gcc48
+
+
+Sample Application Notes
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+This section demonstrates how to launch ``testpmd`` with QLogic 579xx
+devices managed by ``librte_pmd_qede`` in Linux operating system.
+
+#. Request huge pages:
+
+   .. code-block:: console
+
+      echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages/nr_hugepages
+
+#. Load ``igb_uio`` or ``vfio-pci`` driver:
+
+   .. code-block:: console
+
+      insmod ./x86_64-native-linuxapp-gcc/kmod/igb_uio.ko
+
+   or
+
+   .. code-block:: console
+
+      modprobe vfio-pci
+
+#. Bind the QLogic 579xx adapters to ``igb_uio`` or ``vfio-pci`` loaded in the
+   previous step::
+
+      ./tools/dpdk_nic_bind.py --bind igb_uio 0000:84:00.0 0000:84:00.1 0000:84:00.2 0000:84:00.3
+
+   or
+
+   Setup VFIO permissions for regular users and then bind to ``vfio-pci``:
+
+   .. code-block:: console
+
+      sudo chmod a+x /dev/vfio
+
+      sudo chmod 0666 /dev/vfio/*
+
+      ./tools/dpdk_nic_bind.py --bind vfio-pci 0000:84:00.0 0000:84:00.1 0000:84:00.2 0000:84:00.3
+
+#. Start ``testpmd`` with basic parameters:
+
+   .. code-block:: console
+
+      testpmd -c 0xf8000 -n 4 -- -i --nb-cores=4 --portmask=0xf  --rxd=4096 --txd=4096 --txfreet=4068 --rxq=2 --txq=2 --rss-ip --rss-udp
+
+      [...]
+
+    EAL: PCI device 0000:84:00.0 on NUMA socket 1
+    EAL:   probe driver: 1077:1634 rte_qede_pmd
+    EAL:   Not managed by a supported kernel driver, skipped
+    EAL: PCI device 0000:84:00.1 on NUMA socket 1
+    EAL:   probe driver: 1077:1634 rte_qede_pmd
+    EAL:   Not managed by a supported kernel driver, skipped
+    EAL: PCI device 0000:88:00.0 on NUMA socket 1
+    EAL:   probe driver: 1077:1656 rte_qede_pmd
+    EAL:   PCI memory mapped at 0x7f738b200000
+    EAL:   PCI memory mapped at 0x7f738b280000
+    EAL:   PCI memory mapped at 0x7f738b300000
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qed_load_firmware_data: Loading the firmware file /lib/firmware/qed/qed_init_values_zipped.bin...
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_print_adapter_info:Chip details - BB1
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_print_adapter_info:Driver version:QEDE PMD 8.7.9.0_1.0.0
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_print_adapter_info:Firmware version:8.7.7.0
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_print_adapter_info:Management firmware version:8.7.8.0
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_common_dev_init:macaddr 00:0e:1e:d2:08:e8
+    EAL: PCI device 0000:88:00.1 on NUMA socket 1
+    EAL:   probe driver: 1077:1656 rte_qede_pmd
+    EAL:   PCI memory mapped at 0x7f738b310000
+    EAL:   PCI memory mapped at 0x7f738b390000
+    EAL:   PCI memory mapped at 0x7f738b410000
+    [QEDE PMD: (88:00.1:dpdk-port-1)]qede_common_dev_init:macaddr 00:0e:1e:d2:08:e9
+    EAL: PCI device 0000:88:00.2 on NUMA socket 1
+    EAL:   probe driver: 1077:1656 rte_qede_pmd
+    EAL:   PCI memory mapped at 0x7f738b420000
+    EAL:   PCI memory mapped at 0x7f738b4a0000
+    EAL:   PCI memory mapped at 0x7f738b520000
+
+    [QEDE PMD: (88:00.2:dpdk-port-2)]qede_common_dev_init:macaddr 00:0e:1e:d2:08:ea
+    EAL: PCI device 0000:88:00.3 on NUMA socket 1
+    EAL:   probe driver: 1077:1656 rte_qede_pmd
+    EAL:   PCI memory mapped at 0x7f738b530000
+    EAL:   PCI memory mapped at 0x7f738b5b0000
+    EAL:   PCI memory mapped at 0x7f738b630000
+
+    [QEDE PMD: (88:00.3:dpdk-port-3)]qede_common_dev_init:macaddr 00:0e:1e:d2:08:eb
+    Interactive-mode selected
+    Configuring Port 0 (socket 0)
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_tx_queue_setup:txq 0 num_desc 4096 tx_free_thresh 4068 socket 0
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_tx_queue_setup:txq 1 num_desc 4096 tx_free_thresh 4068 socket 0
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_rx_queue_setup:rxq 0 num_desc 4096 rx_buf_size=2148 socket 0
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_rx_queue_setup:rxq 1 num_desc 4096 rx_buf_size=2148 socket 0
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_dev_start:port 0
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_config_rss:RSS flag is set
+    [QEDE PMD: (88:00.0:dpdk-port-0)]qede_dev_start:link status: down
+    Port 0: 00:0E:1E:D2:08:E8
+    Configuring Port 1 (socket 0)
+    [QEDE PMD: (88:00.1:dpdk-port-1)]qede_tx_queue_setup:txq 0 num_desc 4096 tx_free_thresh 4068 socket 0
+    [QEDE PMD: (88:00.1:dpdk-port-1)]qede_tx_queue_setup:txq 1 num_desc 4096 tx_free_thresh 4068 socket 0
+    [QEDE PMD: (88:00.1:dpdk-port-1)]qede_rx_queue_setup:rxq 0 num_desc 4096 rx_buf_size=2148 socket 0
+    [QEDE PMD: (88:00.1:dpdk-port-1)]qede_rx_queue_setup:rxq 1 num_desc 4096 rx_buf_size=2148 socket 0
+    [QEDE PMD: (88:00.1:dpdk-port-1)]qede_dev_start:port 1
+    ...
+    Checking link statuses...
+    Port 0 Link Up - speed 25000 Mbps - full-duplex
+    Port 1 Link Up - speed 25000 Mbps - full-duplex
+    Port 2 Link Up - speed 25000 Mbps - full-duplex
+    Port 3 Link Up - speed 25000 Mbps - full-duplex
+    Done
+    testpmd>
+
+
+SR-IOV: Prerequisites and Sample Application Notes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This section provides instructions to configure SR-IOV with Linux OS.
+
+**Note**: QEDE PMD will be used to bind to SR-IOV VF device and
+        Linux native kernel driver (QEDE) will function as SR-IOV PF driver.
+
+#. Verify SR-IOV and ARI capabilities are enabled on the adapter using ``lspci``:
+
+   .. code-block:: console
+
+      lspci -s <slot> -vvv
+
+   Example output:
+
+   .. code-block:: console
+
+      [...]
+      Capabilities: [1b8 v1] Alternative Routing-ID Interpretation (ARI)
+      [...]
+      Capabilities: [1c0 v1] Single Root I/O Virtualization (SR-IOV)
+      [...]
+      Kernel driver in use: igb_uio
+
+#. Load the kernel module:
+
+   .. code-block:: console
+
+      modprobe qede
+
+   Example output:
+
+   .. code-block:: console
+
+      systemd-udevd[4848]: renamed network interface eth0 to ens5f0
+      systemd-udevd[4848]: renamed network interface eth1 to ens5f1
+
+#. Bring up the PF ports:
+
+   .. code-block:: console
+
+      ifconfig ens5f0 up
+      ifconfig ens5f1 up
+
+#. Create VF device(s):
+
+   Echo the number of VFs to be created into "sriov_numvfs" sysfs entry
+   of the parent PF.
+
+   Example output:
+
+   .. code-block:: console
+
+      echo 2 > /sys/devices/pci0000:00/0000:00:03.0/0000:81:00.0/sriov_numvfs
+
+
+#. Assign VF MAC address:
+
+   Assign MAC address to the VF using iproute2 utility. The syntax is:
+   ip link set <PF iface> vf <VF id> mac <macaddr>
+
+   Example output:
+
+   .. code-block:: console
+
+      ip link set ens5f0 vf 0 mac 52:54:00:2f:9d:e8
+
+
+#. PCI Passthrough:
+
+   The VF devices may be passed through to the guest VM using virt-manager or
+   virsh. QEDE PMD should be used to bind the VF devices in the guest VM
+   using the instructions outlined in the Application notes below.