2. BNX2X Poll Mode Driver

2.6.1. 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_BNX2X_PMD (default y)

  Toggle compilation of bnx2x driver.

• CONFIG_RTE_LIBRTE_BNX2X_DEBUG (default n)

  Toggle display of generic debugging messages.

• CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT (default n)

  Toggle display of initialization related messages.

• CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX (default n)

  Toggle display of transmit fast path run-time messages.

• CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX (default n)

  Toggle display of receive fast path run-time messages.

• CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC (default n)

  Toggle display of register reads and writes.

2.6.2. Driver Compilation

BNX2X 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 BNX2X 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 BNX2X PMD for Linux i686 gcc target, run the following “make” command:

cd <DPDK-source-directory>
make config T=i686-native-linuxapp-gcc install

To compile BNX2X PMD for Linux i686 gcc target, run the following “make” command:

cd <DPDK-source-directory>
make config T=i686-native-linuxapp-gcc install

To compile BNX2X 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 BNX2X 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

To compile BNX2X 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

2.7.1. Linux Installation

2.7.2. Sample Application Notes

This section demonstrates how to launch testpmd with QLogic 578xx devices managed by librte_pmd_bnx2x in Linux operating system.

1. Request huge pages:

   echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages/nr_hugepages
   

2. Load igb_uio or vfio-pci driver:

   insmod ./x86_64-native-linuxapp-gcc/kmod/igb_uio.ko
   

   or

   modprobe vfio-pci
   

3. Bind the QLogic 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
   

   or

   Setup VFIO permissions for regular users and then bind to vfio-pci:

   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
   

4. Start testpmd with basic parameters:

   ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- -i
   

   Example output:

   [...]
   EAL: PCI device 0000:84:00.0 on NUMA socket 1
   EAL:   probe driver: 14e4:168e rte_bnx2x_pmd
   EAL:   PCI memory mapped at 0x7f14f6fe5000
   EAL:   PCI memory mapped at 0x7f14f67e5000
   EAL:   PCI memory mapped at 0x7f15fbd9b000
   EAL: PCI device 0000:84:00.1 on NUMA socket 1
   EAL:   probe driver: 14e4:168e rte_bnx2x_pmd
   EAL:   PCI memory mapped at 0x7f14f5fe5000
   EAL:   PCI memory mapped at 0x7f14f57e5000
   EAL:   PCI memory mapped at 0x7f15fbd4f000
   Interactive-mode selected
   Configuring Port 0 (socket 0)
   PMD: bnx2x_dev_tx_queue_setup(): fp[00] req_bd=512, thresh=512,
                usable_bd=1020, total_bd=1024,
                             tx_pages=4
   PMD: bnx2x_dev_rx_queue_setup(): fp[00] req_bd=128, thresh=0,
                usable_bd=510, total_bd=512,
                             rx_pages=1, cq_pages=8
   PMD: bnx2x_print_adapter_info():
   [...]
   Checking link statuses...
   Port 0 Link Up - speed 10000 Mbps - full-duplex
   Port 1 Link Up - speed 10000 Mbps - full-duplex
   Done
   testpmd>
   

2.7.3. SR-IOV: Prerequisites and sample Application Notes

This section provides instructions to configure SR-IOV with Linux OS.

1. Verify SR-IOV and ARI capabilities are enabled on the adapter using lspci:

   lspci -s <slot> -vvv
   

   Example output:

   [...]
   Capabilities: [1b8 v1] Alternative Routing-ID Interpretation (ARI)
   [...]
   Capabilities: [1c0 v1] Single Root I/O Virtualization (SR-IOV)
   [...]
   Kernel driver in use: igb_uio
   

2. Load the kernel module:

   modprobe bnx2x
   

   Example output:

   systemd-udevd[4848]: renamed network interface eth0 to ens5f0
   systemd-udevd[4848]: renamed network interface eth1 to ens5f1
   

3. Bring up the PF ports:

   ifconfig ens5f0 up
   ifconfig ens5f1 up
   

4. Create VF device(s):

   Echo the number of VFs to be created into “sriov_numvfs” sysfs entry of the parent PF.

   Example output:

   echo 2 > /sys/devices/pci0000:00/0000:00:03.0/0000:81:00.0/sriov_numvfs
   

5. 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:

   ip link set ens5f0 vf 0 mac 52:54:00:2f:9d:e8
   

6. PCI Passthrough:

   The VF devices may be passed through to the guest VM using virt-manager or virsh etc. bnx2x PMD should be used to bind the VF devices in the guest VM using the instructions outlined in the Application notes below.