lshw | A ruby gem for easy access to lshw -xml output

[EDIT-1] clarification of using same interface for DPDK and Kernel routing

Answer> as discussed over comments please refer to DPDKD + kernel on same interface

Based on the information shared there are multiple questions to the single query I'm trying to bypass all traffic to the PMD I'm currently developing. Addressing each one separately below

1. question 1: using dpdk-l2fwd example application

Answer> DPDK application l2fwd application makes use of basic APi with almost no HW offloads. Based on your environment (I have a board with one ethernet interface (eth0)), the right set of parameters should be -p 0x1 --no-mac-updating -T 1. This will configure the application to receive and transmit packet using single DPDK interface (that is eth0 on your board).

Note: DPDK Application can work with DPDK PMD both physical and virtual

1. question 2: I tried to use net_tap, using the following command:

Answer> If the intend is to intercept the traffic from physical and then forward to tap interface, then one needs modify the eal arguments as ./build/l2fwd --vdev=net_tap0,iface="my_eth0" -- -p 0x3 -T 1 --no-mac-updating. This will allow the application to probe physical NXP interface (eth0) and make use of Linux TAP interface as secondary interface. Thus any traffic from NXP and TAP will be cross connected such as NXP (eth0) <==> TAP (my_eth0)

1. question 3: ./usertools/dpdk-devbind.py --status returns empty

Answer> Form the dpdk site supported NIC list NXP dpaa, dpaa2, enetc, enetfec, pfe. Cross checking the kernel driver fsl_dpaa2_eth I think it is safe to assume dpaa2 PMD is supported. As you have mentioned the NIC is not enumerated, it looks like there are certain caveats to such model revision, supported board, BSP package, vendor-sub vendor ID check etc. More details can be found Board Support Package, and DPAA2 NIC guide

Debug & Alternative solutions:

1. To start with use the Kernel Driver to bring in packets
2. Use extra logging and debug to identify why the NIC is shown in the application

Approach 1:

1. Make sure the NIC is bind with kernel driver fsl_dpaa2_eth.
2. ensure NIC is connected and link is up with ethtool eth0
3. set to promiscous mode with ifconfig eth0 promisc up
4. start DPDK application with PCAP PMD, ./build/l2fwd --vdev=net_pcap0,iface=eth0 -- -p 1 --no-mac-updating -T 1
5. Check packet are received and redirected to PCAP eth0 PMD by checking the statistics.

Approach 2:

1. Ideally the NIC should be categorized under network device to be probed by debind.py.
2. Check the device details using lshw -c net -businfo for network.
3. try checking with lspci -Dvmmnnk [PCIe BUS:Slot:Function id] for network details.
4. If above details does not show up as network device this might be reason for not getting listed.

• Suggestions or workaround: You can try to forcefully bind with igb_uio or vfio-pci (I am not much famialr with NXP SoC) by dpdk-devbind -b vfio-pci [PCIe S:B:F]. Then cross check with lspci -ks [PCIe S:B:F]. Once successfully done, one can start dpdk l2fwd in PMD debug mode with ./build/l2fwd -a [PCIe S:B:F] --log-level=pmd,8 -- -p 1 --no-mac-updating | more. Thus by intercepting and interpreting the logs one can identify what is going

Note:

1. It is assumed the application is build with static libraries and not dynamic. To build with static libraries use make static for l2fwd.
2. For the described use case recommended application is basicfwd/skeleton rather than l2fwd.