[dpdk-dev] DPDK 2.2 build failing with vhost-kni
thanks ferruh yigit!! cheers On Mon, Apr 11, 2016 at 2:57 PM, chintu hetam wrote: > I tried vhost-user mode, and during init of ./vhost-switch it fails > with > PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x1528 > pf queue num: 0, configured vmdq pool num: 64, each vmdq pool has 2 queues > EAL: Error - exiting with code: 1 > Cause: Cannot initialize network ports > > it's failing in port_init function, and it seems from > http://dpdk.org/doc/guides-1.8/rel_notes/resolved_issues.html > > this has to with ixgbe checking for eeprom pba parameters. is that > correct, coz rebuilding ixgbe 4.3.13 by disabling those lines dint help > either? > > i tried enabling configure > CONFIG_RTE_LIBRTE_ETHDEV_DEBUG=y > but still i don't see the log messages under /var/log nor on stdout? > > just to keep ball rolling i'd like to see at least kni compiling and > working. > > FYI, i am using X540-AT2 > > cheers > > On Mon, Apr 11, 2016 at 10:09 AM, chintu hetam > wrote: > >> Thanks Xie. >> >> I am trying to test FreeBSD-9.3-virtio as guest. Somewhere in the forum i >> found virtio-kni combination reaching around 2.7 Gbps performance, which is >> enough for my test, though i dint find equivalent driver performance >> characterization for qemu-vhost user space combination. >> Also, as per nics-2.2 user guide, "Linux kernel with KVM module; vhost >> module loaded and ioeventfd supported. Qemu standard backend without vhost >> support isn?t tested, and probably isn?t supported",which is bit different >> from vhost user space support,but still.. >> >> Just to be sure vhost user space = qemu virtio backend- tap-linux-bridge >> configuration, as per nics guide, right? >> >> Thanking in advance, again. >> >> >> >> >> >> >> >> On Mon, Apr 11, 2016 at 4:25 AM, Xie, Huawei >> wrote: >> >>> On 4/10/2016 7:26 AM, chintu hetam wrote: >>> > I am compiling DPDK 2.2 on Fedora 23 and i am seeing following build >>> error >>> > >>> /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c: >>> > In function ?kni_sock_poll?: >>> > >>> /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c:254:25: >>> > error: ?SOCK_ASYNC_NOSPACE? undeclared (first use in this function) >>> > (!test_and_set_bit(SOCK_ASYNC_NOSPACE, >sock->flags) && >>> > ^ >>> >>> Hi, besides the issue, now user space vhost is the preferred way to >>> switch packets with the virtual machine, and we have plans to remove kni >>> vhost support. Do you have any reason to use kni vhost? >>> >> >> >
[dpdk-dev] DPDK 2.2 build failing with vhost-kni
Thanks Xie. I am trying to test FreeBSD-9.3-virtio as guest. Somewhere in the forum i found virtio-kni combination reaching around 2.7 Gbps performance, which is enough for my test, though i dint find equivalent driver performance characterization for qemu-vhost user space combination. Also, as per nics-2.2 user guide, "Linux kernel with KVM module; vhost module loaded and ioeventfd supported. Qemu standard backend without vhost support isn?t tested, and probably isn?t supported",which is bit different from vhost user space support,but still.. Just to be sure vhost user space = qemu virtio backend- tap-linux-bridge configuration, as per nics guide, right? Thanking in advance, again. On Mon, Apr 11, 2016 at 4:25 AM, Xie, Huawei wrote: > On 4/10/2016 7:26 AM, chintu hetam wrote: > > I am compiling DPDK 2.2 on Fedora 23 and i am seeing following build > error > > > /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c: > > In function ?kni_sock_poll?: > > > /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c:254:25: > > error: ?SOCK_ASYNC_NOSPACE? undeclared (first use in this function) > > (!test_and_set_bit(SOCK_ASYNC_NOSPACE, >sock->flags) && > > ^ > > Hi, besides the issue, now user space vhost is the preferred way to > switch packets with the virtual machine, and we have plans to remove kni > vhost support. Do you have any reason to use kni vhost? >
[dpdk-dev] DPDK 2.2 build failing with vhost-kni
I am compiling DPDK 2.2 on Fedora 23 and i am seeing following build error /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c: In function ?kni_sock_poll?: /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c:254:25: error: ?SOCK_ASYNC_NOSPACE? undeclared (first use in this function) (!test_and_set_bit(SOCK_ASYNC_NOSPACE, >sock->flags) && ^ /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c:254:25: note: each undeclared identifier is reported only once for each function it appears in /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c: In function ?kni_sk_write_space?: /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c:622:26: error: ?SOCK_ASYNC_NOSPACE? undeclared (first use in this function) !test_and_clear_bit(SOCK_ASYNC_NOSPACE, ^ /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c: In function ?kni_vhost_backend_init?: /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c:669:38: error: too few arguments to function ?sk_alloc? if (!(q = (struct kni_vhost_queue *)sk_alloc( ^ In file included from /home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.c:27:0: /usr/src/kernels/4.4.6-300.fc23.x86_64/include/net/sock.h:1511:14: note: declared here struct sock *sk_alloc(struct net *net, int family, gfp_t priority, ^ /usr/src/kernels/4.4.6-300.fc23.x86_64/scripts/Makefile.build:258: recipe for target '/home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.o' failed make[8]: *** [/home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni/kni_vhost.o] Error 1 /usr/src/kernels/4.4.6-300.fc23.x86_64/Makefile:1388: recipe for target '_module_/home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni' failed make[7]: *** [_module_/home/vcr/devel/dpdk/dpdk-2.2.0/build/build/lib/librte_eal/linuxapp/kni] Error 2 Makefile:146: recipe for target 'sub-make' failed make[6]: *** [sub-make] Error 2 /home/vcr/devel/dpdk/dpdk-2.2.0/mk/rte.module.mk:79: recipe for target 'rte_kni.ko' failed make[5]: *** [rte_kni.ko] Error 2 /home/vcr/devel/dpdk/dpdk-2.2.0/mk/rte.subdir.mk:61: recipe for target 'kni' failed make[4]: *** [kni] Error 2 /home/vcr/devel/dpdk/dpdk-2.2.0/mk/rte.subdir.mk:61: recipe for target 'linuxapp' failed make[3]: *** [linuxapp] Error 2 /home/vcr/devel/dpdk/dpdk-2.2.0/mk/rte.subdir.mk:61: recipe for target 'librte_eal' failed make[2]: *** [librte_eal] Error 2 /home/vcr/devel/dpdk/dpdk-2.2.0/mk/rte.sdkbuild.mk:77: recipe for target 'lib' failed make[1]: *** [lib] Error 2 /home/vcr/devel/dpdk/dpdk-2.2.0/mk/rte.sdkroot.mk:123: recipe for target 'all' failed make: *** [all] Error 2 it's confirmed it's failing after 1) CONFIG_RTE_KNI_VHOST=y a 2) make config T=x86_64-native-linuxapp-gcc 3) make [root at localhost dpdk-2.2.0]# uname -a Linux localhost.localdomain 4.4.6-300.fc23.x86_64 #1 SMP Wed Mar 16 22:10:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[dpdk-dev] DPDK 2.2 issue with dpdk kni-virtio
Hello All, We are trying to test virtio-vhost-kni performance, I able to start kni application but after that when i looked for /sys/class/net/vEth0, there's no sock_fd and sock_en parameters, hence i am stuck from attaching fd to virtio-qemu. Host: Fedora 23 HugetblsFS: 1G pages Following is my config. [root at localhost dpdk-2.2.0]# ./tools/dpdk_nic_bind.py --status Network devices using DPDK-compatible driver :02:00.2 'I350 Gigabit Network Connection' drv=igb_uio unused=igb :02:00.3 'I350 Gigabit Network Connection' drv=igb_uio unused=igb :86:00.0 'Ethernet Controller 10-Gigabit X540-AT2' drv=igb_uio unused=ixgbe :86:00.1 'Ethernet Controller 10-Gigabit X540-AT2' drv=igb_uio unused=ixgbe Network devices using kernel driver === :02:00.0 'I350 Gigabit Network Connection' if=ens2f0 drv=igb unused=igb_uio *Active* :02:00.1 'I350 Gigabit Network Connection' if=ens2f1 drv=igb unused=igb_uio :89:00.0 'Ethernet Controller 10-Gigabit X540-AT2' if=enp137s0f0 drv=ixgbe unused=igb_uio :89:00.1 'Ethernet Controller 10-Gigabit X540-AT2' if=enp137s0f1 drv=ixgbe unused=igb_uio Other network devices = examples/kni/build/app/kni -c 0xf -n 4 -- -p 0xc -P --config="(2,0,1),(3,2,3)" : : : PP: Port ID: 3 APP: Rx lcore ID: 2, Tx lcore ID: 3 APP: Initialising port 2 ... PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f1d3ffef6c0 sw_sc_ring=0x7f1d3ffef180 hw_ring=0x7f1d3ffefc00 dma_addr=0x533ffefc00 PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f1d3ffdcfc0 hw_ring=0x7f1d3ffdf000 dma_addr=0x533ffdf000 PMD: ixgbe_set_tx_function(): Using simple tx code path PMD: ixgbe_set_tx_function(): Vector tx enabled. PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 4 (port=2). KNI: pci: 86:00:00 8086:1528 APP: Initialising port 3 ... PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f1d3ffcc6c0 sw_sc_ring=0x7f1d3ffcc180 hw_ring=0x7f1d3ffccc00 dma_addr=0x533ffccc00 PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f1d3ffb9fc0 hw_ring=0x7f1d3ffbc000 dma_addr=0x533ffbc000 PMD: ixgbe_set_tx_function(): Using simple tx code path PMD: ixgbe_set_tx_function(): Vector tx enabled. PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 4 (port=3). KNI: pci: 86:00:01 8086:1528 KNI: pci: 86:00:01 8086:1528 Checking link status done Port 2 Link Up - speed 100 Mbps - full-duplex Port 3 Link Up - speed 100 Mbps - full-duplex APP: Lcore 1 is writing to port 2 APP: Lcore 2 is reading from port 3 APP: Lcore 3 is writing to port 3 APP: Lcore 0 is reading from port 2 ls /sys/class/net/vEth2/ addr_assign_type broadcastdev_idduplex ifalias link_mode netdev_group phys_port_name proto_down statistics type address carrier dev_port flags ifindex mtu operstate phys_switch_id queues subsystem uevent addr_len carrier_changes dormant gro_flush_timeout iflink name_assign_type phys_port_id power speed tx_queue_len As this is sysfs, it has to be in kmod, but i don't see any mention of these two parameters, what's going on? Any help on what causes this issue? -thanks-
