Rami- Attached is the results of running testpmd with loglevel=8.
The setting CONFIG_RTE_LIBRTE_VMXNET3_PMD=y seems to be set. # grep 'CONFIG_RTE_LIBRTE_VMXNET3_PMD=y' build/.config CONFIG_RTE_LIBRTE_VMXNET3_PMD=y Should a library be build like /usr/lib64/dpdk-pmds/librte_pmd_vmxnet3.so.1? If so I don't see it. # find /usr/lib64/dpdk-pmds /usr/lib64/dpdk-pmds /usr/lib64/dpdk-pmds/librte_pmd_bnxt.so.2 /usr/lib64/dpdk-pmds/librte_pmd_e1000.so.1 /usr/lib64/dpdk-pmds/librte_pmd_enic.so.1 /usr/lib64/dpdk-pmds/librte_pmd_failsafe.so.1 /usr/lib64/dpdk-pmds/librte_pmd_i40e.so.2 /usr/lib64/dpdk-pmds/librte_pmd_ixgbe.so.2 /usr/lib64/dpdk-pmds/librte_pmd_mlx4.so.1 /usr/lib64/dpdk-pmds/librte_pmd_mlx5.so.1 /usr/lib64/dpdk-pmds/librte_pmd_nfp.so.1 /usr/lib64/dpdk-pmds/librte_pmd_qede.so.1 /usr/lib64/dpdk-pmds/librte_pmd_ring.so.2 /usr/lib64/dpdk-pmds/librte_pmd_softnic.so.1 /usr/lib64/dpdk-pmds/librte_pmd_vhost.so.2 /usr/lib64/dpdk-pmds/librte_pmd_virtio.so.1 Regards, -Jamie On Fri, Sep 7, 2018 at 9:08 AM, Rami Rosen <[email protected]> wrote: > Hi Jamie, > Can you run this with --log-level=8 -w 0000:0b:00.0 -w 0000:13:00.0 > and post the results here? > > (I mean like the following: > testpmd -l 1,2,3 -n 1 --log-level=8 -w 0000:0b:00.0 -w 0000:13:00.0 -- > --disable-hw-vlan --forward-mode=mac > --eth-peer=0,00:00:00:00:33:33 --eth-peer=1,00:00:00:00:44:44 -i > --nb-cores=2 --rxq=8 --txq=8 --rxd=8192 --txd=8192) > > and also to be on the safe side, make sure that > in build/.config you have > CONFIG_RTE_LIBRTE_VMXNET3_PMD=y > (It should be so by default for dpdk-stable-17.11.4) > > Regards, > Rami Rosen > > On Thu, 6 Sep 2018 at 19:39, Jamie Fargen <[email protected]> wrote: > > > > Hello- > > > > Would like to do some performance analysis using testpmd on a RHEL7 > VMWare > > guest using a VMX3NET network devices. Similar tests have been performed > > using RHEL7 KVM guests using VirtIO network devices, but the same process > > does not work with VMX3NET network interfaces. > > > > The dpdk-stable-17.11 has been compiled and it looks like the devices are > > properly bound to the uio driver, but when testpmd is started it is > unable > > to locate the devices. > > > > This is the basic process of how the uio module is loaded, the devices > our > > bound to the driver, and testpmd is started. > > > > [root@redacted ~]# cat startTestPmd17.sh > > #!/bin/bash -x > > modprobe uio > > insmod /root/dpdk-stable-17.11.4/build/kmod/igb_uio.ko > > /root/dpdk-stable-17.11.4/usertools/dpdk-devbind.py -b igb_uio 0b:00.0 > > /root/dpdk-stable-17.11.4/usertools/dpdk-devbind.py -b igb_uio 13:00.0 > > mount -t hugetlbfs nodev /mnt/huge > > echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages- > > 2048kB/nr_hugepages > > testpmd -l 1,2,3 -n 1 -- --disable-hw-vlan --forward-mode=mac > > --eth-peer=0,00:00:00:00:33:33 --eth-peer=1,00:00:00:00:44:44 -i > > --nb-cores=2 --rxq=8 --txq=8 --rxd=8192 --txd=8192 > > > > EAL: Detected 4 lcore(s) > > EAL: No free hugepages reported in hugepages-1048576kB > > EAL: Probing VFIO support... > > EAL: No probed ethernet devices > > Set mac packet forwarding mode > > Interactive-mode selected > > USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=163456, size=2176, > > socket=0 > > Done > > testpmd> > > > > > > There are network devices bound to DPDK-compatible uio driver. > > [root@redacted ~]# dpdk-stable-17.11.4/usertools/dpdk-devbind.py -s > > > > Network devices using DPDK-compatible driver > > ============================================ > > 0000:0b:00.0 'VMXNET3 Ethernet Controller 07b0' drv=igb_uio > unused=vmxnet3 > > 0000:13:00.0 'VMXNET3 Ethernet Controller 07b0' drv=igb_uio > unused=vmxnet3 > > > > Network devices using kernel driver > > =================================== > > 0000:1b:00.0 'VMXNET3 Ethernet Controller 07b0' if=ens256 drv=vmxnet3 > > unused=igb_uio *Active* > > > > > > If anyone has any spare cycles to help me solve this issue it would be > > greatly appreciated. > > > > > > -- > > Jamie Fargen > > Senior Consultant > > [email protected] > > 813-817-4430 > -- Jamie Fargen Senior Consultant [email protected] 813-817-4430
