From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9E251A00E6 for ; Thu, 11 Jul 2019 15:47:58 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6581D322C; Thu, 11 Jul 2019 15:47:57 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 69D2131FC for ; Thu, 11 Jul 2019 15:47:56 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 46EFBA0613; Thu, 11 Jul 2019 15:47:56 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Thu, 11 Jul 2019 13:47:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 19.05 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: tb.bingel@qq.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 319] dpdk-i40e could not receive vlan packet whose ip_len was bigger than 1496 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D319 Bug ID: 319 Summary: dpdk-i40e could not receive vlan packet whose ip_len was bigger than 1496 Product: DPDK Version: 19.05 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: tb.bingel@qq.com Target Milestone: --- Hi, I found dpdk-i40e could not receive vlan packet whose ip_len was bigger than 1496, and I tested the same test cases with i350(igb) network card, NO such issue. Was it a bug in DPDK? Thanks! > Test Environment: * network card: Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP * CPU: Intel(R) Xeon(R) Silver 4116 CPU @ 2.10GHz * OS: Ubuntu 16.04 * DPDK: 19.05 > How to reproduce? ------------------------------------------------------------------------ Step 1: start kni example $ sudo ./build/kni -l 0-5 -n 4 -- -P -p 0x1 -m --config=3D"(0,1,3)"=20 EAL: Detected 48 lcore(s) EAL: Detected 2 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Probing VFIO support... EAL: PCI device 0000:19:00.0 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device 0000:19:00.1 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device 0000:19:00.2 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device 0000:19:00.3 on NUMA socket 0 EAL: probe driver: 8086:1521 net_e1000_igb EAL: PCI device 0000:3b:00.0 on NUMA socket 0 EAL: probe driver: 8086:1583 net_i40e EAL: PCI device 0000:3b:00.1 on NUMA socket 0 EAL: probe driver: 8086:1583 net_i40e APP: Initialising port 0 ... Checking link status ..done Port0 Link Up - speed 40000Mbps - full-duplex APP: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D APP: KNI Running APP: kill -SIGUSR1 90114 APP: Show KNI Statistics. APP: kill -SIGUSR2 90114 APP: Zero KNI Statistics. APP: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D APP: Lcore 1 is reading from port 0 APP: Lcore 2 has nothing to do APP: Lcore 3 is writing to port 0 APP: Lcore 4 has nothing to do APP: Lcore 0 has nothing to do APP: Lcore 5 has nothing to do APP: Configure network interface of 0 up APP: vEth0 NIC Link is Up 40000 Mbps (AutoNeg) Full Duplex. Step 2: configure KNI interface WITHOUT VLAN $ sudo ifconfig vEth0 192.168.99.141/24 Step 3: configure KNI interface WITH VLAN ID $ sudo vconfig add vEth0 589 Added VLAN with VID =3D=3D 589 to IF -:vEth0:- $ sudo ifconfig vEth0 192.168.100.141/24 Step 4: ping KNI IP(no VLAN) from antoher PC $ ping -c 1 -s 1472 -M do 192.168.99.141=20=20=20=20 PING 192.168.99.141 (192.168.99.141) 1472(1500) bytes of data. <<<< It's OK for ip_len 1500 1480 bytes from 192.168.99.141: icmp_seq=3D1 ttl=3D64 time=3D7.53 ms Step 5: ping KNI VLAN IP from anther PC $ ping -c 1 -s 1468 -M do 192.168.100.141=20 PING 192.168.100.141 (192.168.100.141) 1468(1496) bytes of data. <<<< It'= s OK for ip payload 1496 1476 bytes from 192.168.100.141: icmp_seq=3D1 ttl=3D64 time=3D4.66 ms $ ping -c 1 -s 1469 -M do 192.168.100.141=20 PING 192.168.100.141 (192.168.100.141) 1469(1497) bytes of data. <<< fail= ed for ip_len 1497 ^C --- 192.168.100.141 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms ------------------------------------------------------------------------ --=20 You are receiving this mail because: You are the assignee for the bug.=