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 17B538E9C for ; Wed, 4 Nov 2015 16:54:31 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga103.fm.intel.com with ESMTP; 04 Nov 2015 07:54:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,243,1444719600"; d="scan'208";a="843027692" Received: from irsmsx154.ger.corp.intel.com ([163.33.192.96]) by fmsmga002.fm.intel.com with ESMTP; 04 Nov 2015 07:54:28 -0800 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.98]) by IRSMSX154.ger.corp.intel.com ([169.254.12.252]) with mapi id 14.03.0248.002; Wed, 4 Nov 2015 15:54:26 +0000 From: "Van Haaren, Harry" To: Martin Weiser , "dev@dpdk.org" Thread-Topic: [dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK 2.1 Thread-Index: AQHRC9vz+ZflGh3LdUe0W6ZTUC4/PZ6JEEEQgAKZVwCAABQ6cA== Date: Wed, 4 Nov 2015 15:54:26 +0000 Message-ID: References: <56274EFE.5040706@allegro-packets.com> <5639CB88.7040108@allegro-packets.com> In-Reply-To: <5639CB88.7040108@allegro-packets.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-inteldataclassification: CTP_PUBLIC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsIiwiaWQiOiJjM2U3M2RhNC05YTQ4LTRlYTItOGU1Ny04MGMxMTQ2M2Y3N2UiLCJwcm9wcyI6W3sibiI6IkludGVsRGF0YUNsYXNzaWZpY2F0aW9uIiwidmFscyI6W3sidmFsdWUiOiJDVFBfUFVCTElDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiWkJ3WURcLzBaS01sK3FRcFppM2FEdTBGT0puNzE3TzdtYkZ6QVpjcUlXWmc9In0= x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] ixgbe: ierrors counter spuriously increasing in DPDK 2.1 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2015 15:54:32 -0000 > From: Martin Weiser [mailto:martin.weiser@allegro-packets.com] > Subject: Re: [dpdk-dev] ixgbe: ierrors counter spuriously increasing in D= PDK 2.1 > The > rx-error which showed up immediately after starting the interface is > gone since this was probably caused by mac_remote_errors.=20 Improvement - that's good. > But we still > see a huge number of rx-errors although all packets are received > properly and when looking at the extended stats those come from the > rx_l3_l4_xsum_error counter. That is useful information, good to know that statistic is the root cause. > In our setup we are dealing with lots of UDP traffic which does have the > UDP checksum set to 0 (which to my knowledge is allowed for UDP). Yes indeed checksum calculation for UDP is optional, and should be set to z= ero when not performed. > This > traffic seems to cause those rx_l3_l4_xsum_errors. > When doing the same > test with other NICs (e.g. XL710) no rx-errors are accounted. So this is a ixgbe bug, and listed in the errata, item 43 "Integrity Error = Reported for IPv4/UDP Packets with Zero Checksum" in http://www.intel.com/c= ontent/dam/www/public/us/en/documents/specification-updates/82599-10-gbe-co= ntroller-spec-update.pdf=20 > For the generic stats interface I would prefer only packets that could > not be received to be accounted in the rx-error counter regardless of > the actual NIC. What do you think? Agreed. I've sent a patch that removes "xec", the register name for l3_l4_x= sum_errors: http://dpdk.org/dev/patchwork/patch/8678/ Would you test it please? -Harry