From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f174.google.com (mail-ig0-f174.google.com [209.85.213.174]) by dpdk.org (Postfix) with ESMTP id DA6858E8C for ; Fri, 4 Dec 2015 17:15:47 +0100 (CET) Received: by igcmv3 with SMTP id mv3so38994037igc.0 for ; Fri, 04 Dec 2015 08:15:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=djfmfVh0xpFrHiGJpDmqwhQ4zFyGTW7wMFDP+SmNzO0=; b=DQf8fYVKDysPoy6VaNnnnO6NpMxzRVPV6AwDmlaqCNnalfnos1SD4YLNhmy3VQVwP5 NW+9Kg9gcFi0xeMFDNgqjliuDF8wS6xIxRRpc9ieQHMulmT3aE/Es7E6vQPXjbuDgq2B 7WGM4kwYQr0zscetkeNwQtLaFWWI6iroTHKDgvg2hdHOEea7RlMWSTUoIRsxVdZ9V2z9 TnJ70EcID4hnluAoT5L3Tu+QAoeqfXq6TxpfMdBj1e0x3YH3M3hVhioxdnr7a3HIsnes zHd9Fml3mXmrarHyVJh/JmM98pT5XhaV3Ss3Mjig4fgs3CwVZdiUOnfXDUdKKx7KO6QF aglg== X-Received: by 10.50.142.40 with SMTP id rt8mr4933850igb.24.1449245747331; Fri, 04 Dec 2015 08:15:47 -0800 (PST) Received: from [192.168.134.97] ([67.92.53.130]) by smtp.gmail.com with ESMTPSA id eg1sm1611798igb.18.2015.12.04.08.15.46 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Dec 2015 08:15:46 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) From: Ilir Iljazi X-Mailer: iPhone Mail (13B143) In-Reply-To: <3AEA2BF9852C6F48A459DA490692831FF89E31@IRSMSX109.ger.corp.intel.com> Date: Fri, 4 Dec 2015 10:15:46 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <94B45C14-F215-40C3-A241-4AAC4AE15008@gmail.com> References: <3AEA2BF9852C6F48A459DA490692831FF89E31@IRSMSX109.ger.corp.intel.com> To: "Pattan, Reshma" Cc: "users@dpdk.org" Subject: Re: [dpdk-users] DPDK KNI Issue X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2015 16:15:48 -0000 Thanks for the response, I have tried both with and without steps 9 and 10 t= o no avail. There is also no core dump generated. Interestingly, however, th= ere are some dropped packets on the interface but they seem to be occurring i= n a burst when the interface is started but not incrementing throughout the u= ptime of the interface. Tcpdump is executed in most basic mode without filte= rs: #tcpdump -vv -i vEth0=20 Nothing is coming in and as far as I can tell nothing is going out.=20 Ilir > On Dec 4, 2015, at 6:27 AM, Pattan, Reshma wrote= : >=20 > Hi, >=20 > I had tried KNI ping testing on fedora , DPDK2.2 and using one loopback c= onnection, it works fine and I tried without steps 9 and 10. > I am not sure why steps 9 & 10 are needed in your case, but you can try wi= thout those 2 steps and see the results.=20 > Also, after you start the ping, make sure there is no core dump in dmesg f= or KNI module. > If ur running tcpdump with icmp filter try running without filter and firs= t see if ARP packets are reaching to KNI or not. > Also can you check if packet drop stats of kni iface increasing? >=20 > Thanks, > Reshma >=20 >> -----Original Message----- >> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Ilir Iljazi >> Sent: Thursday, December 3, 2015 9:55 PM >> To: users@dpdk.org >> Subject: [dpdk-users] DPDK KNI Issue >>=20 >> Hi, >> I have been having an issue with dpdk kni whereby I cant send and receive= >> packets from the kni interface. I spent about a week trying to figure it o= ut the >> issue myself to no avail. Although I did find articles with a similar sig= nature to >> mine none of the proposed solutions helped solve the problem. >>=20 >> Environment: >> Ubuntu Server 14.04 >> DPDK Package 2.1.0 (Latest) >> Network Card: (10Gbe ixgbe driver) >>=20 >> 06:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP= + >> Network Connection >> 06:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP= + >> Network Connection >>=20 >> 06.00.0 (port 0 connected to switch) >> 06:00.1 (port 1 not connected to switch) >>=20 >> Configuration: >> 1.) DPDK built without issue >> 2.) Modules Loaded: >>=20 >> insmod $RTE_TARGET/kmod/igb_uio.ko >> insmod $RTE_TARGET/kmod/rte_kni.ko kthread_mode=3Dmultiple >>=20 >>=20 >> 3.) Reserved Huge Pages: >>=20 >> echo 4096 > >> /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages >> echo 4096 > >> /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages >>=20 >>=20 >> 4.) Mounted huge page partition >>=20 >> echo ">>> Mounting huge page partition" >> mkdir -p /mnt/huge >> mount -t hugetlbfs nodev /mnt/huge >>=20 >>=20 >> 5.) Interfaces 06:00.0/1 bound to igb uio module (option 19 on setup) >>=20 >> Network devices using DPDK-compatible driver >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> 0000:06:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=3Digb_u= io >> unused=3D >> 0000:06:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=3Digb_u= io >> unused=3D >>=20 >>=20 >> 6.) Started kni test application: >>=20 >> Command: ./examples/kni/build/app/kni -n 4 -c 0xff -- -p 0x1 -P -- >> config=3D"(0,5,7)" & >>=20 >> Output: >>=20 >> EAL: PCI device 0000:06:00.0 on NUMA socket -1 >> EAL: probe driver: 8086:10fb rte_ixgbe_pmd >> EAL: PCI memory mapped at 0x7fcda5c00000 >> EAL: PCI memory mapped at 0x7fcda5c80000 >> PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5 >> PMD: eth_ixgbe_dev_init(): port 0 vendorID=3D0x8086 deviceID=3D0x10fb >> EAL: PCI device 0000:06:00.1 on NUMA socket -1 >> EAL: probe driver: 8086:10fb rte_ixgbe_pmd >> EAL: PCI memory mapped at 0x7fcda5c84000 >> EAL: PCI memory mapped at 0x7fcda5d04000 >> PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6 >> PMD: eth_ixgbe_dev_init(): port 1 vendorID=3D0x8086 deviceID=3D0x10fb >> APP: Port ID: 0 >> APP: Rx lcore ID: 5, Tx lcore ID: 7 >> APP: Initialising port 0 ... >> PMD: ixgbe_dev_rx_queue_setup(): sw_ring=3D0x7fcd5c1adcc0 >> sw_sc_ring=3D0x7fcd5c1ad780 hw_ring=3D0x7fcd5c1ae200 dma_addr=3D0xe5b1ae2= 00 >> PMD: ixgbe_dev_tx_queue_setup(): sw_ring=3D0x7fcd5c19b5c0 >> hw_ring=3D0x7fcd5c19d600 dma_addr=3D0xe5b19d600 >> 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 burs= t size >> no less than 32. >> KNI: pci: 06:00:00 8086:10fb >>=20 >>=20 >> Checking link status >> done >> Port 0 Link Up - speed 10000 Mbps - full-duplex >> APP: Lcore 1 has nothing to do >> APP: Lcore 2 has nothing to do >> APP: Lcore 3 has nothing to do >> APP: Lcore 4 has nothing to do >> APP: Lcore 5 is reading from port 0 >> APP: Lcore 6 has nothing to do >> APP: Lcore 7 is writing to port 0 >> APP: Lcore 0 has nothing to do >>=20 >>=20 >> 7.) KNI interface configured and brought up: >>=20 >> root@l3sys2-acc2-3329:~/dpdk-2.1.0# ifconfig vEth0 192.168.13.95 netmask >> 255.255.248.0 up >> APP: Configure network interface of 0 up >> PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burs= t size >> no less than 32. >>=20 >> root@l3sys2-acc2-3329:~/dpdk-2.1.0# ifconfig vEth0 >>=20 >> vEth0 Link encap:Ethernet HWaddr 90:e2:ba:55:fd:c4 >> inet addr:192.168.13.95 Bcast:192.168.15.255 Mask:255.255.248.= 0 >> inet6 addr: fe80::92e2:baff:fe55:fdc4/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:8 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>=20 >> Note also that dmesg is clean not pointing to any issues: >> [ 1770.113952] KNI: /dev/kni opened >> [ 1770.561957] KNI: Creating kni... >> [ 1770.561973] KNI: tx_phys: 0x0000000e5b1ca9c0, tx_q addr: >> 0xffff880e5b1ca9c0 >> [ 1770.561974] KNI: rx_phys: 0x0000000e5b1c8940, rx_q addr: >> 0xffff880e5b1c8940 >> [ 1770.561975] KNI: alloc_phys: 0x0000000e5b1c68c0, alloc_q addr: >> 0xffff880e5b1c68c0 >> [ 1770.561976] KNI: free_phys: 0x0000000e5b1c4840, free_q addr: >> 0xffff880e5b1c4840 >> [ 1770.561977] KNI: req_phys: 0x0000000e5b1c27c0, req_q addr: >> 0xffff880e5b1c27c0 >> [ 1770.561978] KNI: resp_phys: 0x0000000e5b1c0740, resp_q addr: >> 0xffff880e5b1c0740 >> [ 1770.561979] KNI: mbuf_phys: 0x000000006727dec0, mbuf_kva: >> 0xffff88006727dec0 >> [ 1770.561980] KNI: mbuf_va: 0x00007fcd8627dec0 >> [ 1770.561981] KNI: mbuf_size: 2048 >> [ 1770.561987] KNI: pci_bus: 06:00:00 >> [ 1770.599689] igb_uio 0000:06:00.0: (PCI Express:5.0GT/s:Width x8) [ >> 1770.599691] 90:e2:ba:55:fd:c4 [ 1770.599777] igb_uio 0000:06:00.0 (unnam= ed >> net_device) (uninitialized): >> MAC: 2, PHY: 0, PBA No: E68793-006 >> [ 1770.599779] igb_uio 0000:06:00.0 (unnamed net_device) (uninitialized):= >> Enabled Features: RxQ: 1 TxQ: 1 >> [ 1770.599790] igb_uio 0000:06:00.0 (unnamed net_device) (uninitialized):= >> Intel(R) 10 Gigabit Network Connection >>=20 >>=20 >> 8.) ethtool vEth0 link is detected: >>=20 >> root@l3sys2-acc2-3329:~/dpdk-2.1.0# ethtool vEth0 Settings for vEth0: >> Supported ports: [ FIBRE ] >> Supported link modes: 10000baseT/Full >> Supported pause frame use: No >> Supports auto-negotiation: No >> Advertised link modes: 10000baseT/Full >> Advertised pause frame use: No >> Advertised auto-negotiation: No >> Speed: 10000Mb/s >> Duplex: Full >> Port: Other >> PHYAD: 0 >> Transceiver: external >> Auto-negotiation: off >> Supports Wake-on: d >> Wake-on: d >> Current message level: 0x00000007 (7) >> drv probe link >> Link detected: yes >>=20 >>=20 >> 9.) kernel started with: iommu=3Dpt intel_iommu=3Don >>=20 >> GRUB_CMDLINE_LINUX=3D"iommu=3Dpt intel_iommu=3Don console=3Dtty1 >> console=3DttyS1,115200n8" >>=20 >>=20 >> 10.) Disabled virtualization in BIOS per forum recommendation >>=20 >>=20 >> Situation: >> Despite doing everything seemingly correct I cant ssh or ping to and from= this >> interface. I tried starting tcpdump on the interface but didn't notice an= y traffic. >> I'm not sure what I'm doing wrong here, if I could get some support I'd >> appreciate it. I can provide additional details from the system if needed= . >>=20 >> Thanks!