From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 8CB632B86 for ; Mon, 1 Aug 2016 09:13:06 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga103.fm.intel.com with ESMTP; 01 Aug 2016 00:13:06 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,454,1464678000"; d="scan'208";a="1032745953" Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25]) by fmsmga002.fm.intel.com with ESMTP; 01 Aug 2016 00:13:04 -0700 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by irsmsx110.ger.corp.intel.com (163.33.3.25) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 1 Aug 2016 08:13:03 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.204]) by irsmsx111.ger.corp.intel.com ([169.254.2.113]) with mapi id 14.03.0248.002; Mon, 1 Aug 2016 08:13:03 +0100 From: "Lal, PrzemyslawX" To: Alec Istomin , "users@dpdk.org" Thread-Topic: [dpdk-users] i40e: issues with TCP Segmenation Offload of VLAN-tagged traffic Thread-Index: AQHR6bn+/RCyny5IMU2yrTjMkUOo4KAzskVg Date: Mon, 1 Aug 2016 07:13:02 +0000 Message-ID: References: <0b17d48ce8dc4b7f9c2deca394a88a16@SEAEXCHMBX06.olympus.F5Net.com> In-Reply-To: <0b17d48ce8dc4b7f9c2deca394a88a16@SEAEXCHMBX06.olympus.F5Net.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] i40e: issues with TCP Segmenation Offload of VLAN-tagged traffic 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: Mon, 01 Aug 2016 07:13:07 -0000 Hi Alec, Thanks for your reply. I know about issues with VLAN tagged traffic on i40e= - I also know this workaround and tried it before posting here, but unfort= unately this doesn't solve problems with TSO + VLAN. MTU is already set to = 1450 on all network interfaces on the path and issue is still there. Thanks, Przemek -----Original Message----- From: Alec Istomin [mailto:A.Istomin@F5.com]=20 Sent: Friday, July 29, 2016 6:55 PM To: Lal, PrzemyslawX ; users@dpdk.org Subject: RE: [dpdk-users] i40e: issues with TCP Segmenation Offload of VLAN= -tagged traffic Przemek, Please try to reduce MTU on your virtio interfaces and see if this changes= the behavior. I had to use mtu 1496 to allow tagged connectivity in my en= vironment. Make sure to restart OVS after MTU change. I did not use TSO (it's not working in OVS 2.5 and dpdk 2.2.0 that i use),= but the symptoms look very familiar. Regards, Alec -----Original Message----- From: users [mailto:users-bounces@dpdk.org] On Behalf Of Lal, PrzemyslawX Sent: Friday, July 29, 2016 6:45 To: users@dpdk.org Cc: Kavanagh, Mark B ; Ksiadz, MarcinX ; Siddiqui, Muhammad A Subject: [dpdk-users] i40e: issues with TCP Segmenation Offload of VLAN-tag= ged traffic Hi, I have problem with TCP Segmentation Offload of VLAN tagged traffic on i40e= PMD driver - connectivity dies after trying to send first packet. After spawning new VM non-TCP traffic (like ping) works fine. After trying = to connect using SSH to the VM, connectivity is completely broken on i40e -= even ping stops working. In the meanwhile connection between VMs connected= to the same OVS using vhost-user ports works fine.=20 This is how topology looks like (simplified): virtio virtio <-- TSO enabled on the virtio interface o= n virtual machine | | vhostuser vhostuser <-- TSO supported for vhost-user interfac= es in DPDK since 16.04 release | | ovs-dpdk ovs-dpdk <-- VLAN tagging/untagging done in OVS-DP= DK using OpenFlow rules | | rte_i40e_pmd rte_i40e_pmd <-- first packet that should be offloaded= breaks connectivity | | +----TOR switch----+ Problem occurs only with i40e NIC - when using exactly the same configurati= on with ixgbe NIC everything works fine, it looks like i40e PMD driver caus= es this problem. Versions tested: DPDK - 16.04, 16.07-rc3, also some post 16.07-rc2 master tested with this p= atch applied http://dpdk.org/ml/archives/dev/2016-July/043924.html OVS-DPDK - recent versions from master branch with TSO RFC patch applied on= top - link: http://openvswitch.org/pipermail/dev/2016-June/072871.html In each case TSO and VLAN combo on ixgbe was working with no issues, on i40= e it was always broken. Issue was also independently reproduced by Mark Kavanagh (cc'd). Is this known issue and is there any way to solve this issue? If not, are t= here any plans to fix this problem in the upcoming DPDK releases? =09 Best Regards, Przemek