Does anyone have some suggestions on where to start with this ? When we run this using DPDK 17.05, the ports come up fine for our design and testpmd. However, with 17.11, the ports to not come up and I end up with undefined rx_pkt_burst/tx_pkt_burst functions as shown here:
(gdb) p rte_eth_devices[0] $1 = { rx_pkt_burst = 0x0, tx_pkt_burst = 0x0, tx_pkt_prepare = 0x0, data = 0x7f46c31b7640, dev_ops = 0xab0580 <virtio_eth_dev_ops>, device = 0x7f46c40240e0, intr_handle = 0x7f46c40241b8, link_intr_cbs = { tqh_first = 0x7f46c318a200, tqh_last = 0x7f46c318a200 }, post_rx_burst_cbs = {0x0 <repeats 1024 times>}, pre_tx_burst_cbs = {0x0 <repeats 1024 times>}, state = RTE_ETH_DEV_ATTACHED, security_ctx = 0x0 } Here is the sequence for testpmd using 17.11: root:/# dpdk-devbind -s Network devices using DPDK-compatible driver ============================================ 0000:00:06.0 'Virtio network device 1000' drv=uio_pci_generic unused=vfio-pci 0000:00:07.0 'Virtio network device 1000' drv=uio_pci_generic unused=vfio-pci Network devices using kernel driver =================================== 0000:00:03.0 'Virtio network device 1000' if=eth0 drv=virtio-pci unused=vfio-pci,uio_pci_generic Other Network devices ===================== <none> Crypto devices using DPDK-compatible driver =========================================== <none> Crypto devices using kernel driver ================================== <none> Other Crypto devices ==================== <none> Eventdev devices using DPDK-compatible driver ============================================= <none> Eventdev devices using kernel driver ==================================== <none> Other Eventdev devices ====================== <none> Mempool devices using DPDK-compatible driver ============================================ <none> Mempool devices using kernel driver =================================== <none> Other Mempool devices ===================== <none> root:/# testpmd -c 7 -n 3 -b 0000:00:03.0 -- -i --nb-cores=2 --nb-ports=2 EAL: Detected 4 lcore(s) EAL: Probing VFIO support... EAL: VFIO support initialized EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles ! EAL: PCI device 0000:00:03.0 on NUMA socket -1 EAL: Device is blacklisted, not initializing EAL: PCI device 0000:00:06.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 1af4:1000 net_virtio EAL: PCI device 0000:00:07.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 1af4:1000 net_virtio Interactive-mode selected USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=163456, size=2176, socket=0 Configuring Port 0 (socket 0) EAL: Unknown handle type of fd 20 EAL: Unknown handle type of fd 20 Fail to start port 0 Configuring Port 1 (socket 0) EAL: Unknown handle type of fd 22 EAL: Unknown handle type of fd 22 Fail to start port 1 Please stop the ports first Done testpmd> Mike Bly | Principal Software Engineer/Architect, Packet Software & Access - Advanced Development m...@ciena.com<mailto:m...@ciena.com> | 12730 E. Mirabeau Pkwy | Spokane Valley, WA 99216 Direct +1.509.242.9246 | Fax +1.509.242.9001