From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 8B0CC2C60 for ; Mon, 1 Aug 2016 14:15:06 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga104.fm.intel.com with ESMTP; 01 Aug 2016 05:15:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,455,1464678000"; d="scan'208";a="1032891230" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga002.fm.intel.com with ESMTP; 01 Aug 2016 05:15:05 -0700 Received: from fmsmsx115.amr.corp.intel.com (10.18.116.19) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 1 Aug 2016 05:15:05 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by fmsmsx115.amr.corp.intel.com (10.18.116.19) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 1 Aug 2016 05:15:04 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.181]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.116]) with mapi id 14.03.0248.002; Mon, 1 Aug 2016 20:15:03 +0800 From: "Tan, Jianfeng" To: "Lal, PrzemyslawX" , Alec Istomin , "users@dpdk.org" Thread-Topic: [dpdk-users] i40e: issues with TCP Segmenation Offload of VLAN-tagged traffic Thread-Index: AQHR6boI51+0YaKQFkO2sxBkNh7V3aAzLrcAgADZM1A= Date: Mon, 1 Aug 2016 12:15:02 +0000 Message-ID: References: <0b17d48ce8dc4b7f9c2deca394a88a16@SEAEXCHMBX06.olympus.F5Net.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] 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 12:15:07 -0000 Usually, IMHO, PING works well and TCP does not, which means L4 checksum is= not correctly calculated. On the receive side, you can use tcpdump to see = if any packets (possible wrong L4 checksum) packets are received. Of course= , you can also check statistics of the flow, if there are any packets go th= rough. Thanks, Jianfeng > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Lal, > PrzemyslawX > Sent: Monday, August 1, 2016 3:13 PM > To: Alec Istomin; users@dpdk.org > Subject: Re: [dpdk-users] i40e: issues with TCP Segmenation Offload of > VLAN-tagged traffic >=20 > Hi Alec, >=20 > Thanks for your reply. I know about issues with VLAN tagged traffic on i4= 0e - I > also know this workaround and tried it before posting here, but > unfortunately 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 ther= e. >=20 > Thanks, > Przemek >=20 > -----Original Message----- > From: Alec Istomin [mailto:A.Istomin@F5.com] > 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 >=20 > Przemek, > Please try to reduce MTU on your virtio interfaces and see if this chang= es the > behavior. I had to use mtu 1496 to allow tagged connectivity in my > environment. Make sure to restart OVS after MTU change. >=20 > 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. >=20 > Regards, > Alec >=20 > -----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- > tagged traffic >=20 > Hi, >=20 > I have problem with TCP Segmentation Offload of VLAN tagged traffic on i4= 0e > PMD driver - connectivity dies after trying to send first packet. > After spawning new VM non-TCP traffic (like ping) works fine. After tryin= g 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): >=20 > virtio virtio <-- TSO enabled on the virtio interface= on virtual > machine > | | > vhostuser vhostuser <-- TSO supported for vhost-user interf= aces in > DPDK since 16.04 release > | | > ovs-dpdk ovs-dpdk <-- VLAN tagging/untagging done in OVS-= DPDK > using OpenFlow rules > | | > rte_i40e_pmd rte_i40e_pmd <-- first packet that should be offload= ed > breaks connectivity > | | > +----TOR switch----+ >=20 > Problem occurs only with i40e NIC - when using exactly the same > configuration with ixgbe NIC everything works fine, it looks like i40e PM= D > driver causes this problem. >=20 > Versions tested: > DPDK - 16.04, 16.07-rc3, also some post 16.07-rc2 master tested with this > patch 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 >=20 > In each case TSO and VLAN combo on ixgbe was working with no issues, on > i40e it was always broken. >=20 > Issue was also independently reproduced by Mark Kavanagh (cc'd). >=20 > Is this known issue and is there any way to solve this issue? If not, are= there > any plans to fix this problem in the upcoming DPDK releases? >=20 > Best Regards, > Przemek